On Tue, Sep 22, 2009 at 1:38 PM, Pete Emerson <pemer...@gmail.com> wrote: > > I'm using 0.24 with Webrick (in the process of migrating to 0.25 / passenger). > > Occasionally, the puppetmasterd becomes unavailable, and we see error > messages along the lines of: > > Could not call puppetmaster.getconfig: #<Errno::ECONNRESET: Connection > reset by peer> > > I believe the puppetmasterd does not completely die, so it is still in > the process list. > > I'm wondering what a good way to monitor this would be. > > I see that I can telnet into port 8140, is there something simple I > can send that would give me an indication that everything is okay or > not? > > Any suggestions on monitoring this would be appreciated. > > Pete
Strangely enough, we had a similar situation here. Whenever Puppet (the client) would reload its own configs, it would die and not start again. So we wrote a nice little nagios script that monitored whether puppet was running on each machine. From that, we could restart or send an email or anything we want really. Cheers, Clint --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
