On Fri, Sep 4, 2009 at 2:08 PM, David Rosenstrauch<[email protected]> wrote: > On 09/04/2009 02:50 PM, Jonathan Call wrote: >> Since I have a large Nagios distributed system the possibility of a >> Nagios process going AWOL on one of my many servers is a serious >> concern. Has anyone come up with a sure way to confirm (i.e. a cron job) >> that Nagios is processing checks properly? >> >> For example, I had one OCP_daemon process die, as a result the Nagios >> process hung for quite some time before it was discovered. Freshness >> checking is not an option because many hosts are behind firewalls or on >> private networks and so the central server has active checks disabled >> globally. >> >> Jonathan > > See the check_nagios plugin. One of the parms you can specify is to > have it check how long ago it wrote something to its log file. > > We recently had a problem where our Nagios box went down and we never > got any notifictions. So I set up another small Nagios instance whose > sole purpose is to monitor the primary instance. It has just one > service check: check_nrpe calling check_nagios on the main Nagios box > to verify that it's up and running. > > HTH, > > DR > > ------------------------------------------------------------------------------
You could also set up a check with an external provider. Websitepulse.com for example. This way it takes everything outside of your environment and it should be set up to send a message to your phone directly via sms for example. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
