You might want to have a look at: http://projects.reductivelabs.com/issues/1934
to add exit codes to puppetd --onetime runs at least. Otherwise you should implement reports and examine those I guess. On Tue, Aug 25, 2009 at 5:52 PM, chakkerz<chakk...@gmail.com> wrote: > > Hello there > > I have puppet managing a fair few hosts but because we are still > testing (and later for peace of mind) we'd like to hear from hosts > that are failing their puppet run. > > I had a look at the configuration reference on reductivelabs but i > can't see anything that appears relevant. Does anyone know if there is > something i can set to notify me or a fact through $yamldir that > indicates that on a particular host, something is wrong. So, the > puppet run did not complete because of an error. > > Oh, i'm using puppetd daemonized ... if i was still running it through > cron there would be a way. > > Something i just thought of was monit - which i could get to look at > the log ... but that seems to be a rather long way around... > > Any thoughts? > Cheers > chakkerz > > > -- Nigel Kersten nig...@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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
