What about checking the last-update times of the /var/lib/puppet.....yaml files on the puppetmaster? I've looked at this manually just to see if a host stopped checking in, but not automated anything.
On Tue, Aug 25, 2009 at 9:21 PM, Ohad Levy <ohadl...@gmail.com> wrote: > a few options > > 1. if you dont have a lot of clients, use the build in tagmail report which > sends email with every change. > 2. write your own custom puppet report that does something. > 3. parse the reports and import them to a db whatever > 4. wait a bit until the puppet web interface is ready ;) > > Ohad > > > > On Wed, Aug 26, 2009 at 8:52 AM, 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 >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---