On Thu, Feb 12, 2009 at 6:19 PM, Larry Ludwig <larry...@gmail.com> wrote: > > Yea I want to make sure puppetmaster returns some sort of valid > result. Though the monit for memory leaks is not a bad idea. > > More than just pinging a port.
We have some python I've been meaning to try and get published that do a slightly better job that this. Basically I'm faking out the required XMLRPC headers for an authenticated client on the machines themselves and issuing a listing of the facts mountpoint for each mongrel instance (because I'm on the localhost we can do this) so we can then publish this data via our local monitoring system daemon. I've got a background job of working on trying to fake out a proper getconfig request for a catalog to check timing data, but that's not functional yet. If you sit down and look at the traffic, either de-encrypting with ssldump or simply monitoring the unencrypted traffic between your SSL frontend and the puppet backends (assuming you're using that sort of a setup) you can see the actual conversation is reasonably simple to mimic. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
