> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Jay R. Ashworth > Sent: Tuesday, April 29, 2008 10:25 AM > To: [email protected] > Subject: Re: [Nagios-users] Issue with Contacts and Notifications > > On Tue, Apr 29, 2008 at 09:26:03AM -0500, Marc Powell wrote: > > It sure sounds like you're not editing what you think you're editing > > (i.e. that template isn't used by nagios or the services you think > > you're changing). Please provide specific details or we're just going to > > be guessing randomly. > > > > Template definition > > Service definition > > Contactgroup definition > > Contact definition > > Nagios.cfg line where templates.cfg is included as a cfg_file. > > 'pwd; ls -l templates.cfg' in the directory it lives in. > > 'ps -efwww | grep nagios' output (or whatever ps variant your system > > uses) > > Is there a verbose version of checkconfig that will tell you what > Nagios *thinks you told it to do*? (IE: not just that it's happy with > the config)
Not really. nagios -v will give you counts of objects found, and in the case of the OP, it should be easy to tell if it sees all his expected contacts. In the broader case, Andreas Ericsson once wrote a little program to print out the cfg files that nagios would read. It's available at http://oss.op5.se/nagios/getnagioscfg.c. It was written with 2.x in mind but I don't expect there to have been significant changes for 3.x -- Marc ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ 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
