I seem to have resolved it now. It seems to have been a combination of issues. 1) I use the C based snmp checks, and the command.cfg file was pointing to the perl based check scripts 2) Net-SNMP was not installed on the distributed box
Thanks for all the help guys Rob -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marc Powell Sent: Thursday, November 15, 2007 12:32 PM To: [email protected] Subject: Re: [Nagios-users] submit_check_result always critical > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Robert Gil > Sent: Thursday, November 15, 2007 10:21 AM > To: Robert Gil; Thomas Guyot-Sionnest > Cc: [email protected] > Subject: Re: [Nagios-users] submit_check_result always critical > > I still get the same results from the nagios checks. Is there some kind > of debug mode that I can see the actual results from the nagios checks > to see whether nagios is legitimately reporting those services as > critical? You need to be looking at your distributed nagios box when doing this but I'm quite certain it is based on what you've indicated so far. You should see that in the web interface on that box and in nagios.log. If you still want to go the debug route and you're using nagios-2, you'll need to recompile, passing debug options to ./configure. --enable-DEBUG0 shows function entry and exit --enable-DEBUG1 shows general info messages --enable-DEBUG2 shows warning messages --enable-DEBUG3 shows scheduled events (service and host checks... etc) --enable-DEBUG4 shows service and host notifications --enable-DEBUG5 shows SQL queries --enable-DEBUGALL shows all debugging messages With nagios-3, there are debug options in nagios.cfg. Instead of going this route, I'd make a simple change to the command definitions that are failing on your distributed nagios box, especially the one you previously sent that returns 'no output!'. At the end of the command line, add '2>&1' to capture STDERR from the plugin run. In the web interface/nagios log, you should then see why it's failing. For example (completely off the top of my head) -- define command { command_name check_ping command_line $USER1$/check_ping -H $HOSTADDRESS$ -w 10,50% -c 20,100% 2>&1 # note, the above is all one line } Alternately, running the plugins on your distributed box, as the nagios user, exactly as they're defined in the command{} definition, using appropriate substitutions, should be informative as well... You haven't shown us any actual host/server/command definitions related to your core issue yet so we can't really be specifically helpful there. -- Marc ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
