How to bootstrap munki and get the .com.googlecode.munki.checkandinstallatstartup file ?

[Avasquez3593]

After following this tutorial https://code.google.com/p/munki/wiki/BootstrappingWithMunki

and creating a DS script that indicates the following:

 #!/bin/sh

touch "/Volumes/${DS_LAST_SELECTED_TARGET}/Users/Shared/.com.googlecode.munki.checkandinstallatstartup"

exit 0

Munki still does not bootstrap after rebooting. My managedInstalls.plist file has been configured and placed in the workflow as well along with the script being the last to execute in the workflow . 

Would anyone happen to know why my bootstrap is not successful or at least give me an idea of how I can even start to resolve this problem.

Also considering the script has the following path /Users/Shared/.com.googlecode.munki.checkandinstallatstartup" how do I even get that file in that folder. I am thinking that Munki may not be bootstrapping because that file is not there.

[Gregory Neagle]

> On Dec 8, 2015, at 2:48 PM, Avasquez3593 <avasqu...@gmail.com> wrote:
>
> After following this tutorial https://code.google.com/p/munki/wiki/BootstrappingWithMunki
> and creating a DS script that indicates the following:
>
> #!/bin/sh
> touch "/Volumes/${DS_LAST_SELECTED_TARGET}/Users/Shared/.com.googlecode.munki.checkandinstallatstartup"
>
> exit 0

Any reason you did not simply use the package referenced from that same page? https://github.com/munki/contrib/blob/master/munki_kickstart.pkg?raw=true

>
>
> Munki still does not bootstrap after rebooting. My managedInstalls.plist file has been configured and placed in the workflow as well along with the script being the last to execute in the workflow .
> Would anyone happen to know why my bootstrap is not successful or at least give me an idea of how I can even start to resolve this problem.
>
> Also considering the script has the following path /Users/Shared/.com.googlecode.munki.checkandinstallatstartup" how do I even get that file in that folder. I am thinking that Munki may not be bootstrapping because that file is not there.

Would be easy to check:

ls -al /Users/Shared/

-Greg

[Avasquez3593]

Just to confirm, so you are saying that I do not need the com.googlecode.munki.checkandinstallatstartup file to be in the user/shared folder in order to get Munki to bootstrap. 

As long as I install the package first that you just referenced  and then execute the script after rebooting then it should work.?

[Gregory Neagle]

On Dec 9, 2015, at 9:50 AM, Avasquez3593 <avasqu...@gmail.com> wrote:

Just to confirm, so you are saying that I do not need the com.googlecode.munki.checkandinstallatstartup file to be in the user/shared folder in order to get Munki to bootstrap. 

You _do_ need that file in place. The package _installs_ that file. That’s something packages are really good at doing.

As long as I install the package first that you just referenced  and then execute the script after rebooting then it should work.?

Don’t execute a script. Just install the package.

-Greg

[Nick McSpadden]

In order for the Munki bootstrap to trigger, this file must exist:
/Users/Shared/.com.googlecode.munki.checkandinstallatstartup

There are different ways to get that file into place.  You yourself provided one way - doing it by script that uses touch to put it there.

Greg provided a second (safer) way, which is a package that places that file there.

Whatever method you want to do that gets that file there will work, but as Greg says, the package is a much safer and less fragile means of accomplishing it.  If you're already using DeployStudio, it's trivial to add one more package into the workflow, which is far easier than trying to script the same process.

On Wed, Dec 9, 2015 at 9:50 AM, Avasquez3593 <avasqu...@gmail.com> wrote:

Just to confirm, so you are saying that I do not need the com.googlecode.munki.checkandinstallatstartup file to be in the user/shared folder in order to get Munki to bootstrap. 

As long as I install the package first that you just referenced  and then execute the script after rebooting then it should work.?

--
You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To post to this group, send email to munki-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/f54f447e-434e-4c23-80c2-fbe398cc127d%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

--
Nick McSpadden
nmcsp...@gmail.com

[Amanda Vasquez]

Thanks! I will definitely try this method of adding this package to my workflow in addition to my managedinstalls.plist file  and remove the current script. 

You received this message because you are subscribed to a topic in the Google Groups "munki-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/munki-discuss/eA-oxwuvaCo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to munki-discus...@googlegroups.com.

To post to this group, send email to munki-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/CAJySx-khE_Dkfeh6e4UdgUTFPS8mXX%2B5PYLackeCQw-Q%3DEoc5g%40mail.gmail.com.

[Avasquez3593]

I added this package to the workflow, removed the previous mentioned script and left my managedInstalls.plist file as is in the workflow but Munki bootstrap still does not start. When i open up Managed Software Center i am receiving the following error:

" Update check failed. Managed software center cannot contact the update server at this time. Try again later. if this situation continues, contact your systems administrator."

When i try accessing my munki repo via the web using the url http://ip address/munki_repo  it works without a problem. When I enter the following command in terminal: 

sudo /usr/local/munki/managedsoftwareupdate the software updates install without a problem..

[Nick McSpadden]

To clarify, did you try running sudo /usr/local/munki/managedsoftwareupdate on the same machine that failed to bootstrap, right afterwards?

Do you have any kind of special network configuration that might be interfering? A proxy server, 802.1x, or wireless config that might be active yet?

--

You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To post to this group, send email to munki-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/6a308e47-8bc6-43be-8462-13829738b4b5%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Avasquez3593]

The following error occurs when entering this command on the client machine:

sudo /usr/local/munki/managedsoftwareupdate

WARNING: Improper use of the sudo command could lead to data loss

or the deletion of important system files. Please double-check your

typing when using sudo. Type "man sudo" for more information.

To proceed, enter your password, or type Ctrl-C to abort.

Password:

Managed Software Update Tool

Copyright 2010-2014 The Munki Project

https://github.com/munki/munki

Starting...

WARNING: Client is configured to use the default repo, which is insecure. Client could be trivially compromised when off your organization's network. Consider using a non-default URL, and preferably an https:// URL.

ERROR: managedsoftwareupdate: server check for http://munki/repo failed: [Errno 8] nodename nor servname provided, or not known

[Mr. Alan Siu]

It looks as if your client is configured to use http://munki/repo and not your actual http://youripaddress/munki_repo

Alan Siu

Client Systems Analyst

St. Ignatius College Preparatory

--

You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To post to this group, send email to munki-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/5b20f2fd-3e01-4cec-be9c-2e16c239167a%40googlegroups.com.

[Nick McSpadden]

Based on that error message, your ManagedInstalls.plist isn't being placed. Munki is complaining it's not configured with a SoftwareRepoURL, so it's using the default ('http://munki/repo').

Verify that your ManagedInstalls.plist is going into /Library/Preferences/ during image time.

On Thu, Dec 10, 2015 at 11:01 AM, Avasquez3593 <avasqu...@gmail.com> wrote:

--

You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To post to this group, send email to munki-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/5b20f2fd-3e01-4cec-be9c-2e16c239167a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Avasquez3593]

It finally worked after indicating the path /Library/Preferences/ in DS Admin. You guys are amazing and really great at what you do. Thanks for your help!