We had this issue while we were using webrick and ended up with the
following in cron running every 15 minutes:
if [ `/usr/bin/puppetlast |grep -v puppetlast |sort -n -k 4 |head -n
1|awk '{print \$4}'` -ge 15 ]; then /etc/init.d/puppetmaster restart ;fi
- Jeff
On 09/22/2009 02:38 PM, Pete Emerson 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
>
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
