Re: [Nagios-users] Debugging Nagios?
EUREEKA!!! Thanks to some other users for pointing this out and helping me resolve... Somehow when I converted config files from Nagios 1.x to 2.9, my timeperiods.cfg was messed up and had the 24x7 entry going from 0:00-0:00 everyday, when it should have been 0:00-24:00 everyday. This caused all my checks to be scheduled at midnight everyday. Thanks for all the help with debugging flags and config files. Klaus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bonaparte, Klaus Sent: Wednesday, June 13, 2007 12:18 PM To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Debugging Nagios? nagios.log and syslog were of no value, but I was able to build with debug (./configure --enable-DEBUGALL) and see where Nagios is forcing all checks to occur at midnight tomorrow. I've seen several posts on this with questions, but no answers. Does anyone know how to fix the scheduling in Nagios so it does not schedule all checks at midnight every day? output below is from running 'bin/nagios -s etc/nagios.cfg' with debug on. Notice that all checks are scheduled for midnight tomorrow. Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 ... Host 'snazphoe04' should not be scheduled Host 'sncaanah01' should not be scheduled Host 'sncaanah02' should not be scheduled Host 'sncaanah03' should not be scheduled Host 'sncasacr01' should not be scheduled Host 'sncasacr02' should not be scheduled ... Total scheduled service checks: 502 Service check interval total:928800 Average service check interval: 185
Re: [Nagios-users] Debugging Nagios?
nagios.log and syslog were of no value, but I was able to build with debug (./configure --enable-DEBUGALL) and see where Nagios is forcing all checks to occur at midnight tomorrow. I've seen several posts on this with questions, but no answers. Does anyone know how to fix the scheduling in Nagios so it does not schedule all checks at midnight every day? output below is from running 'bin/nagios -s etc/nagios.cfg' with debug on. Notice that all checks are scheduled for midnight tomorrow. Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 Preferred Time: 1181761343 --> Wed Jun 13 19:02:23 2007 Next Valid Time: 1181779200 --> Thu Jun 14 00:00:00 2007 ... Host 'snazphoe04' should not be scheduled Host 'sncaanah01' should not be scheduled Host 'sncaanah02' should not be scheduled Host 'sncaanah03' should not be scheduled Host 'sncasacr01' should not be scheduled Host 'sncasacr02' should not be scheduled ... Total scheduled service checks: 502 Service check interval total:928800 Average service check interval: 1850.20 sec Service inter-check delay: 3.59 sec Total scheduled service checks: 502 Total hosts:61 Service Interleave factor: 9 Total scheduled services: 502 Service Interleave factor: 9 Total service interleave blocks: 56 Service inter-check delay: 3.6 -Original Message- From: Brian A. Seklecki [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 13, 2007 9:40 AM To: Bonaparte, Klaus Cc: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Debugging Nagios? What a great question! Well there's nagios.log in /var/spool/nagios, use_syslog=1 log_event_handlers=1 log_i
Re: [Nagios-users] Debugging Nagios?
What a great question! Well there's nagios.log in /var/spool/nagios, use_syslog=1 log_event_handlers=1 log_initial_states=1 log_external_commands=1 log_passive_checks=1 log_notifications=1 log_service_retries=1 But getting debug out the schedule probably requires a debug build of the binary. ~~BAS PS It could be worse, you could be trying to debug a plugin/module. On Tue, 2007-06-12 at 18:57 -0400, Bonaparte, Klaus wrote: > ou debug Nagios to determine why it is no longer running any checks? > > I see checks scheduled in the queue, but then time passes and they get > removed from the top of the queue as if they were run but their status > never changes, nothing is logged in nagios.log or syslogs, and once in > a while you can see nagios processes running? > > > > Any help? Debug flags or common things to look for? > -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
[Nagios-users] Debugging Nagios?
How do you debug Nagios to determine why it is no longer running any checks? I see checks scheduled in the queue, but then time passes and they get removed from the top of the queue as if they were run but their status never changes, nothing is logged in nagios.log or syslogs, and once in a while you can see nagios processes running? Any help? Debug flags or common things to look for? Klaus - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] Debugging nagios checks?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jason, Pretty much what I ended up doing, except I just tee'd a copy of the output to a file. Michael On Dec 9, 2005, at 1:02 PM, Jason Rojas wrote: what about using /bin/echo to echo the command to check the syntax, then run the plugin by hand from command line to see if there are any issues? -Jason Hugo van der Kooij wrote: On Fri, 9 Dec 2005, Michael T. Halligan wrote: Yes, yes, and yes. From here, I'm somewhat out of good paths for debugging this. What I can't understand, is I don't even see script processes actually running if I keep a constant ps going.. does Nagios-2 no longer run scripts in a visible manner? It may just be too fast for you to see. I started top. Choose to check only processes of user nagios and did increase the update frequency to 0.5 seconds Then you can see the checks being sparked of. Hugo. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDmiHtwjCqooJyNAMRAk4tAJ0YjkIoc1B3xl/VGFBKfPFD7pa3YQCgsvck K9q7+oolq6d/8o08APV01nw= =Mevl -END PGP SIGNATURE- --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] Debugging nagios checks?
what about using /bin/echo to echo the command to check the syntax, then run the plugin by hand from command line to see if there are any issues? -Jason Hugo van der Kooij wrote: On Fri, 9 Dec 2005, Michael T. Halligan wrote: Yes, yes, and yes. From here, I'm somewhat out of good paths for debugging this. What I can't understand, is I don't even see script processes actually running if I keep a constant ps going.. does Nagios-2 no longer run scripts in a visible manner? It may just be too fast for you to see. I started top. Choose to check only processes of user nagios and did increase the update frequency to 0.5 seconds Then you can see the checks being sparked of. Hugo. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] Debugging nagios checks?
On Fri, 9 Dec 2005, Michael T. Halligan wrote: > > Yes, yes, and yes. From here, I'm somewhat out of good paths for > debugging this. What I can't understand, is I don't even see script > processes actually running if I keep a constant ps going.. does > Nagios-2 no longer run scripts in a visible manner? It may just be too fast for you to see. I started top. Choose to check only processes of user nagios and did increase the update frequency to 0.5 seconds Then you can see the checks being sparked of. Hugo. -- I hate duplicates. Just reply to the relevant mailinglist. [EMAIL PROTECTED] http://hvdkooij.xs4all.nl/ Don't meddle in the affairs of magicians, for they are subtle and quick to anger. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] Debugging nagios checks?
On Fri, 9 Dec 2005, Eli Stair wrote: > Have you already tested the plugin from the commandline, passing it the > args that are sent from Nagios to make sure your version/community > string and mountpoint info are properly read and returned? > > Have you checked to make sure that SNMP is monitoring disk usage? My plan of attack on an existing situation would be: 1. Use snmpwalk to obtain all SNMP data from the host and verify it is presenting disk info. 2. Trace from Service definition to Check command to the actual plugin how the test is done. 3. Retry the plugin manually with the information obtained from the previous two steps. When building one new I would: 1. Use snmpwalk to get all the details. 2. Use the plugin manually to get the proper results. 3. Write a check command 4. Write a service definition Actually this morning I added the check_snmp_int.pl script this way to define a host named internet based on the actual state of the DSL link of my router. Just be carefull of typos. I spend almost an hour before I noticed $ARG2$ is not $ARGS2$ and noticed it just about when I did write a full description for the mailinglist of my problem. Hugo. -- I hate duplicates. Just reply to the relevant mailinglist. [EMAIL PROTECTED] http://hvdkooij.xs4all.nl/ Don't meddle in the affairs of magicians, for they are subtle and quick to anger. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] Debugging nagios checks?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eli, Yes, yes, and yes. From here, I'm somewhat out of good paths for debugging this. What I can't understand, is I don't even see script processes actually running if I keep a constant ps going.. does Nagios-2 no longer run scripts in a visible manner? Michaeel On Dec 9, 2005, at 11:48 AM, Eli Stair wrote: Have you already tested the plugin from the commandline, passing it the args that are sent from Nagios to make sure your version/ community string and mountpoint info are properly read and returned? Have you checked to make sure that SNMP is monitoring disk usage? /eli Michael T. Halligan wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm trying to use check_snmp_storage.pl from http:// www.manubulon.com/ nagios/snmp_storage.html and am having a bit of a hard time. Nagios simply fails when trying to check, with the extremely helpful error of "(No output!)" .. Nothing useful gets generated in any of the logs (and I have every log option turned on).. When I strace nagios, there's still not much useful. How can I make nagios show me what it's running when it runs a check, and show me the output, so I can debug this issue? I think I'm running into a problem with snmp on my client boxes, but I have no idea. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDmd5ywjCqooJyNAMRAsoSAJ9LJhdN5qFYyiUo0yLgYBTP5k+CagCeJjbd l/4YsXHAUJdkgUWEAv3kLf4= =KY95 -END PGP SIGNATURE- --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDmeFJwjCqooJyNAMRAuBrAKC4mwCyldVwnhGiGhjPMvs/RMhsbwCcCgpj uYeR7aShALcHnLoCBtHPUTc= =SvA5 -END PGP SIGNATURE- --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] Debugging nagios checks?
Have you already tested the plugin from the commandline, passing it the args that are sent from Nagios to make sure your version/community string and mountpoint info are properly read and returned? Have you checked to make sure that SNMP is monitoring disk usage? /eli Michael T. Halligan wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm trying to use check_snmp_storage.pl from http://www.manubulon.com/ nagios/snmp_storage.html and am having a bit of a hard time. Nagios simply fails when trying to check, with the extremely helpful error of "(No output!)" .. Nothing useful gets generated in any of the logs (and I have every log option turned on).. When I strace nagios, there's still not much useful. How can I make nagios show me what it's running when it runs a check, and show me the output, so I can debug this issue? I think I'm running into a problem with snmp on my client boxes, but I have no idea. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDmd5ywjCqooJyNAMRAsoSAJ9LJhdN5qFYyiUo0yLgYBTP5k+CagCeJjbd l/4YsXHAUJdkgUWEAv3kLf4= =KY95 -END PGP SIGNATURE- --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
[Nagios-users] Debugging nagios checks?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm trying to use check_snmp_storage.pl from http://www.manubulon.com/ nagios/snmp_storage.html and am having a bit of a hard time. Nagios simply fails when trying to check, with the extremely helpful error of "(No output!)" .. Nothing useful gets generated in any of the logs (and I have every log option turned on).. When I strace nagios, there's still not much useful. How can I make nagios show me what it's running when it runs a check, and show me the output, so I can debug this issue? I think I'm running into a problem with snmp on my client boxes, but I have no idea. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDmd5ywjCqooJyNAMRAsoSAJ9LJhdN5qFYyiUo0yLgYBTP5k+CagCeJjbd l/4YsXHAUJdkgUWEAv3kLf4= =KY95 -END PGP SIGNATURE- --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
