Update check failed - here is a configuration problem...

[mtol...@gmail.com]

Hi,

I have a Munki setup that I'm using for managing around 200 Macs. Munki runs on Yosemite Server and it's been working great but as usually is, there are still some issues that need attention.

My basic deployment workflow for new Macs starts in DeployStudio that I'm using to drop thin base-image (10.10.5), MunkiTools and settings for Munki (munki_repo and manifest).

After DS has finalized installation, I log in and launch Managed Software Center. Most of my manifests include some mandatory apps like munkireport, inventory client and profile for setting up certs and network as Managed Installs. These install as expected and everything seems to work fine.

Next step is usually Optional Installs and this is when something unexpected happens. When I select app and hit Install, MSC shows error message:

“Update check failed

There is a configuration problem with the managed software installer. Could not start the process. Contact your systems administrator.”

MSC quit and relaunch doesn't fix this. However restarting Mac does and error doesn't reappear. Optional Installs work as expected after restart as well as Managed Installs. Also this happens only on workflows that has Managed Installs.

As the error message states, it looks like Managed Installs somehow 'knocks out' launchd for Optional Installs.

I've done some troubleshooting and also browsed previous threads of similar issues but couldn't find exact solution.

So far this is what I got:

MunkiTools 2.3.1.2535

DeployStudio Server 1.6.16

MunkiAdmin 1.3.0

Before launching MSC for the first time, launchd's are like this:

sudo launchctl list | grep munki

- 0 com.googlecode.munki.logouthelper

- 0 com.googlecode.munki.managedsoftwareupdate-check

- 0 com.googlecode.munki.managedsoftwareupdate-manualcheck

- 0 com.googlecode.munki.managedsoftwareupdate-install

After Managed Installs are done and at least one Optional Install has been selected for installation...

sudo launchctl list | grep munki

- 0 com.googlecode.munki.logouthelper

- 0 com.googlecode.munki.managedsoftwareupdate-check

- 1 com.googlecode.munki.managedsoftwareupdate-manualcheck

- 0 com.googlecode.munki.managedsoftwareupdate-install

After MSC GUI failed to install Firefox (or any other optional install) I ran the command below.

/usr/local/munki/managedsoftwareupdate -vvv —installonly

Sep 16 2015 09:42:45 -0700     **Processing self-serve choices**

Sep 16 2015 09:42:45 -0700     Need to install Firefox

Sep 16 2015 09:42:45 -0700     Downloading Firefox-40.0.3.dmg from apps/firefox/fi/Firefox-40.0.3.dmg

Sep 16 2015 09:42:45 -0700     Downloading Firefox-40.0.3.dmg from apps/firefox/fi/Firefox-40.0.3.dmg

Sep 16 2015 09:42:45 -0700     Downloading Firefox-40.0.3.dmg...

Sep 16 2015 09:42:47 -0700     Verifying package integrity...

Sep 16 2015 09:42:47 -0700     Firefox-40.0.3.dmg downloaded at 75335 KB/s

Sep 16 2015 09:42:47 -0700 ###    End managed software check    ###

Sep 16 2015 09:42:47 -0700     

Sep 16 2015 09:42:47 -0700     The following items will be installed or upgraded:

Sep 16 2015 09:42:47 -0700         + Firefox-40.0.3

Sep 16 2015 09:42:47 -0700             Mozilla Firefox is a free and open source web browser.

Sep 16 2015 09:42:47 -0700 Finishing...

This is where the log's Firefox-related entries usually end. For some reason, usually after waiting some time, installation will success and Firefox disappears from the pending updates list of MSC GUI. GUI however still gives the exact same error if I hit Check again button.

Sep 16 2015 09:43:56 -0700 ### Beginning managed installer session ###

Sep 16 2015 09:43:56 -0700 Processing installs

Sep 16 2015 09:43:56 -0700 Installing Mozilla Firefox Finnish (1 of 1)

Sep 16 2015 09:43:56 -0700     Mounting disk image Firefox-40.0.3.dmg

Sep 16 2015 09:44:06 -0700     Copying Firefox.app to /Applications/Firefox.app

Sep 16 2015 09:44:15 -0700     Setting owner for '/Applications/Firefox.app' to 'root'

Sep 16 2015 09:44:15 -0700     Setting group for '/Applications/Firefox.app' to 'admin'

Sep 16 2015 09:44:15 -0700     Setting mode for '/Applications/Firefox.app' to 'o-w'

Sep 16 2015 09:44:15 -0700     The software was successfully installed.

Sep 16 2015 09:44:15 -0700 ###    End managed installer session    ###

This is not a show stopper as one failed install and restarting Mac resolves this issue. Still would be nice to know if this is some configuration problem or expected behaviour.

Thanks in advance.

Mikko

[Erik Gomez]

Are you updating the munki tools via munki during your initial bootstrap and possibly reinstalling the launchd component?

Sent from my iPhone

--
Find related discussion groups here:
https://github.com/munki/munki/wiki/Discussion-Group
---
You received this message because you are subscribed to the Google Groups "munki-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-dev+...@googlegroups.com.
To post to this group, send email to munk...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mtol...@gmail.com]

Yes. MunkiTools components are in manifest as Managed Updates. If I read the log correctly, it looks like launchd doesn't get reinstalled. Still it might have something to do with the error. Good point.

Here's the part of the log:

Sep 16 2015 09:42:44 -0700     **Checking for managed updates**

Sep 16 2015 09:42:44 -0700     munkitools-4.1.2518 requires munkitools_core. Getting info on munkitools_core...

Sep 16 2015 09:42:44 -0700     munkitools_core-2.3.0.2519 requires munkitools_launchd. Getting info on munkitools_launchd...

Sep 16 2015 09:42:44 -0700     munkitools_launchd version 2.0.0.1969 (or newer) is already installed.

Sep 16 2015 09:42:44 -0700     munkitools_core version 2.3.0.2519 (or newer) is already installed.

Sep 16 2015 09:42:44 -0700     munkitools_admin version 2.3.0.2519 (or newer) is already installed.

Sep 16 2015 09:42:44 -0700     munkitools-4.1.2518 requires munkitools_launchd. Getting info on munkitools_launchd...

Sep 16 2015 09:42:44 -0700     munkitools version 4.1.2518 (or newer) is already installed.

[Gregory Neagle]

If this only happens immediately after imaging with DeployStudio, goes away upon reboot and does not come back, it sounds like the Munki tools are getting installed or updated as part of the DeployStudio finalization but the machine is not being rebooted after the tools are installed/updated, and therefore the Munki launchdaemons are not operational or are out-of-date.

Some additional detail on Munki’s launchd components: https://github.com/munki/munki/wiki/LaunchD-Jobs-and-Changing-When-Munki-Runs

-Greg

[mtol...@gmail.com]

Thanks for the reply. Did some more testing over the weekend and after reading the Munki launchd-documentation over again, finally managed to find the culprit. One of the managed installs I have in the manifest, installed launchd-item but didn't require restart. After removing installer in question from the managed installs, problem disappeared. After adding mandatory postinstall restart action for the installer in question, everything is working nice and smooth. Thanks again!

Mikko