Hello List, I''m running puppet on OS X Tiger 10.4.11. When using the launchd plist to start up puppet, I''m frequently seeing this issue where launchd will start up puppet very early in the boot process, often before configd can set the hostname on the client. This results in cert requests for "localhost" on the puppetmaster, and the clients aren''t able to communicate until puppetd is restarted on the client, at which point it uses the correct name and works fine. To get around this, I have switched to using a systemstarter script to start puppet so that it runs late enough not to cause this problem. Is there a way to configure launchd (or puppet) to work around this? I don''t see any way to set dependancies or ordering of processes with launchd but perhaps I am missing something. Has anyone else experienced this? Thanks, Daniel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Nigel Kersten
2009-May-26 16:52 UTC
[Puppet Users] Re: launchd starting up puppetd too early
I think the simplest answer for your case is to switch your launchd plist around to not call puppet directly, but to instead call a script that checks whether the right services are in place before actually starting the first puppet run. Alternatively, given that it sounds like this is only a problem for you on first run, you could do something like we do, where we have a loginhook that runs on first user login that downloads puppet and installs it, then runs puppet. We only have network user accounts, so we know that if a user is logging in for the first time, then we know the network is available. The lack of dependency in launchd can kind of suck sometimes. Unfortunately while we have sophisticated control over KeepAlive where you can specify the value for KeepAlive is dependent upon the NetworkState, you can''t set this for RunAtLoad. On Tue, May 26, 2009 at 9:37 AM, Daniel Koblas <itsupport@chrisking.com> wrote:> > Hello List, > > I''m running puppet on OS X Tiger 10.4.11. When using the launchd > plist to start up puppet, I''m frequently seeing this issue where > launchd will start up puppet very early in the boot process, often > before configd can set the hostname on the client. This results in > cert requests for "localhost" on the puppetmaster, and the clients > aren''t able to communicate until puppetd is restarted on the client, > at which point it uses the correct name and works fine. To get > around this, I have switched to using a systemstarter script to start > puppet so that it runs late enough not to cause this problem. Is > there a way to configure launchd (or puppet) to work around this? I > don''t see any way to set dependancies or ordering of processes with > launchd but perhaps I am missing something. Has anyone else > experienced this? > > Thanks, > Daniel > > > > >-- Nigel Kersten nigelk@google.com System Administrator Google, Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---