Hi all, I setup a puppetmaster host and several clients. I don''t want them to do "stuff" in the background, but just when I tell them to. So for this reason I''m running puppetd manually like this: puppetd --server $SERVER --ignorecache --verbose --onetime --no-daemonize Question 1: when I run this remotely, is there a way to know if puppetd was successful or not without looking at syslog? It seems the exit status is always 0 no matter what. Question 2: I also noticed that sometimes I have to run it twice to get all the changes through. That might be because of errors in the manifests, but I''ve seen that happen also when everything should be fine. Is there a reason for this? I''m running 0.24.5. Thanks, -- Cosimo -- 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.
On Thu, Feb 4, 2010 at 7:00 AM, Cosimo Streppone <cosimo@streppone.it>wrote:> Hi all, > > I setup a puppetmaster host and several clients. > I don''t want them to do "stuff" in the background, > but just when I tell them to. > > So for this reason I''m running puppetd manually like this: > > puppetd --server $SERVER --ignorecache --verbose --onetime --no-daemonize > > you can just use --test, this is an alias for --onetime, --verbose, and--no-daemonize> Question 1: when I run this remotely, is there a way to know if puppetd > was successful or not without looking at syslog? > It seems the exit status is always 0 no matter what. > >use reports: [puppetd] report=true [puppetmasterd] report=store,tagmail now you can check the reports created on the server to see what has happened. You could also configure tagmail to send you an email if any errors occur on any of the puppetd runs.> Question 2: I also noticed that sometimes I have to run it twice to get > all the changes through. That might be because of errors in the manifests, > but I''ve seen that happen also when everything should be fine. > Is there a reason for this? >this should never be required. Possibly you are not using the require/before/notify/subscribe metaparameters to specify the correct ordering?> > I''m running 0.24.5. > > this is a pretty old version, you should think about upgrading. 0.25.4 ispretty stable.> Thanks, > > -- > Cosimo > > -- > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- 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.
On Feb 4, 2010, at 9:29 PM, Dan Bode wrote:> Question 2: I also noticed that sometimes I have to run it twice to get > all the changes through. That might be because of errors in the manifests, > but I''ve seen that happen also when everything should be fine. > Is there a reason for this? > > this should never be required. Possibly you are not using the require/before/notify/subscribe metaparameters to specify the correct ordering?Wellll.... not "never", right? If you have added tools that a provider needs to enable itself (say, the ''gem'' executable) , puppet won''t pick it up until its next initialisation. I''ve also seen ldap dependencies not get picked up immediately after binding, so for instance creating user directories which auto-require that user to exist will fail until the next run. The first one might be addressable with some introspection, like a metaparameter to signal puppet to re-initialise without exiting, the second one looks pretty much like a race condition that one could probably sleep() around in an exec. -=Eric -- 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.
On Thu, Feb 4, 2010 at 11:39 PM, Eric Sorenson <ahpook@gmail.com> wrote:> > On Feb 4, 2010, at 9:29 PM, Dan Bode wrote: > > Question 2: I also noticed that sometimes I have to run it twice to get >> all the changes through. That might be because of errors in the manifests, >> but I''ve seen that happen also when everything should be fine. >> Is there a reason for this? >> > > this should never be required. Possibly you are not using the > require/before/notify/subscribe metaparameters to specify the correct > ordering? > > > Wellll.... not "never", right? >never = almost never.> If you have added tools that a provider needs to enable itself (say, the > ''gem'' executable) , puppet won''t pick it up until its next initialisation. > I''ve also seen ldap dependencies not get picked up immediately after > binding, so for instance creating user directories which auto-require that > user to exist will fail until the next run. >this is true> The first one might be addressable with some introspection, like a > metaparameter to signal puppet to re-initialise without exiting, the second > one looks pretty much like a race condition that one could probably sleep() > around in an exec. >I hadnt considered cases where your dependencies have to sync with an external source.> -=Eric > > -- > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- 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.