Re: [Nagios-users] ping hanging.
On Mon, 9 Jan 2006, Hammond, Robin-David%KB3IEN wrote: -rw-r- 1 nagios nagios 1335 Jan 7 04:30 resource.cfg -rw-rw 1 nagios nagios 1335 Jan 7 04:27 resource.cfg-sample It looks like all the (relevant) files are available for reading. And resorce,cfg is not relevant? Are you 250% sure everything runs as nagios user? Just for arguments sake could you `chmod o+r` these files? Can you trace down the config sections for us? How did you define the service/host? How did you define the check? How did you define the variables? 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=7637alloc_id=16865op=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] ping hanging.
I changed the permission, but it still hangs. did two updates in the web interface, and froze. webpage still reloads, but the data are stale. load averages: 1.17, 1.32, 1.27 06:57:54 55 processes: 1 runnable, 49 sleeping, 4 stopped, 1 on processor CPU states: 0.0% user, 100% nice, 0.0% system, 0.0% interrupt, 0.0% idle Memory: 118M Act, 59M Inact, 756K Wired, 8340K Exec, 159M File, 488K Free Swap: 129M Total, 129M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPUCPU COMMAND 3378 nagios280 184K 948K CPU0:00 0.00% 0.00% top 1345 nagios180 188K4K pause 0:00 0.00% 0.00% csh 3476 nagios100 2500K 1392K wait 0:00 0.00% 0.00% nagios 1346 nagios100 584K 1320K wait 0:00 0.00% 0.00% bash 1454 nagios100 140K 580K STOP 0:00 0.00% 0.00% sh 1099 nagios 40 120K 680K STOP 0:00 0.00% 0.00% ping 3771 nagios 20 2500K 932K STOP 0:00 0.00% 0.00% nagios 4336 nagios 20 228K 724K STOP 0:00 0.00% 0.00% check_ping im using the minimal.cfg file. On Mon, 9 Jan 2006, Hugo van der Kooij wrote: Date: Mon, 9 Jan 2006 23:21:59 +0100 (CET) From: Hugo van der Kooij [EMAIL PROTECTED] Reply-To: nagios-users@lists.sourceforge.net To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] ping hanging. On Mon, 9 Jan 2006, Hammond, Robin-David%KB3IEN wrote: -rw-r- 1 nagios nagios 1335 Jan 7 04:30 resource.cfg -rw-rw 1 nagios nagios 1335 Jan 7 04:27 resource.cfg-sample It looks like all the (relevant) files are available for reading. And resorce,cfg is not relevant? Are you 250% sure everything runs as nagios user? Just for arguments sake could you `chmod o+r` these files? Can you trace down the config sections for us? How did you define the service/host? How did you define the check? How did you define the variables? 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=7637alloc_id=16865op=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 Microsoft: Where do you want to go tomorrow? Linux: Where do you want to go today? BSD: Are you guys coming, or what? Robin-David Hammond KB3IEN www.aresnyc.org. --- 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=7637alloc_id=16865op=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] ping hanging.
Hello, On 1/7/2006 10:32 PM, Marc Powell wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:nagios-users- [EMAIL PROTECTED] On Behalf Of Hammond, Robin-David%KB3IEN Sent: Friday, January 06, 2006 10:02 PM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] ping hanging. ... /Warning: Attempting to execute the command /check_ping -H 4400::34 -w 3000.0,80% -c 5000.0,100% -p 1 -t 10 -6 resulted in a return code of 127. Make sure the script or binary you are trying to execute actually exists... over and over. this is particularly confusiong as i never reran configure nor did I ever uninstall the /check_ping programme it is still in place and executable. Hmm. I *really* hope you never installed the plugins in your root directory. Any ideas? Return code 127 means that the plugin was not found in the location specified in the command definition. Nagios is apparently trying to execute /check_ping and not /path/to/check_ping (usually /usr/local/nagios/libexec/check_ping). There are four primary possibilities -- 1) your command definition does not utilize the $USER1$ macro in the command_line i.e. 'command_line $USER1$/check_ping -H ...' 2) you have manually specified the incorrect path in the command_line i.e. 'command line /check_ping -H ...' 3) $USER1$ is not set to the correct plugins path in resource.cfg 4) you have not included resource.cfg as a resource_file in nagios.cfg One other possibility I encountered: When the resource.cfg file is not readable by nagios, the above happens after nagios reloaded its configuration. The initial configuration file access happens before nagios drops its rights (when started as root), but afterwards, during operation, it's simply no longer permitted to read the resource.cfg... he easy work-around is a chown on the file followed by another configuration reload. Arno -- Marc --- 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_idv37alloc_id865op=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 -- IT-Service Lehmann[EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de --- 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=7637alloc_id=16865op=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] ping hanging.
On Sat, 7 Jan 2006, Hammond, Robin-David%KB3IEN wrote: In order to try to diagnose the nagios problem whereby it enteres the wait state indefinitely, i added some debugging code to commands.c, and rebuilt nagios 2.0rc1. I am now getting a very strange error /Warning: Attempting to execute the command /check_ping -H 4400::34 -w 3000.0,80% -c 5000.0,100% -p 1 -t 10 -6 resulted in a return code of 127. Make sure the script or binary you are trying to execute actually exists... If check_ping calls the normal ping utility you will need to rewrite it for IPv6. Your normal ping will not handle IPv6 addresses. That will be the job of ping6 on most systems. And 4400:34 may be valid syntax for a IPv6 address. But to the best of my knowledge it is not a valid IPv6 address. Valid ranges will be 2000:: untill 3fff:: for public addreses and fe80:: and upwards for link-local addresses. And check_host does work on IPv6 addresses as I have several IPv6 only systems in my setup which I can contact just fine. A manual test here: ./check_ping -H 2001:888:10fa:1 -w 100,20% -c 500,50% check_ping: Invalid hostname/address - 2001:888:10fa:1 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=7637alloc_id=16865op=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] ping hanging.
On Sat, 7 Jan 2006, Hugo van der Kooij wrote: And 4400:34 may be valid syntax for a IPv6 address. Should read 4400::34 and not 4400:34 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=7637alloc_id=16865op=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] ping hanging.
On Sat, 7 Jan 2006, Hugo van der Kooij wrote: A manual test here: ./check_ping -H 2001:888:10fa:1 -w 100,20% -c 500,50% check_ping: Invalid hostname/address - 2001:888:10fa:1 I must have run out of coffee. It works in fact well for IPv6 here: ./check_ping -H 2001:888:10fa::1 -w 100,20% -c 500,50% PING OK - Packet loss = 0%, RTA = 0.20 ms Just need to learn how to type with a low-coffee indicator. Anyone got a plugin for caffeine levels? 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=7637alloc_id=16865op=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] ping hanging.
load averages: 1.52, 1.44, 1.33 16:41 60 processes: 1 runnable, 54 sleeping, 4 stopped, 1 on processor CPUstates: 0.0% user, 96.6% nice, 2.1% system, 1.3% interrupt, 0.0% idle Memory: 102M Act, 48M Inact, 888K Wired, 8708K Exec, 132M File, 26M Free Swap: 129M Total, 129M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPUCPU COMMAND 10070 nagios180 188K 776K pause 0:00 0.00% 0.00% csh 25520 nagios100 568K 1388K wait 0:00 0.00% 0.00% bash 25664 nagios100 2500K 1328K wait 0:00 0.00% 0.00% nagios 24737 nagios100 140K 580K STOP 0:00 0.00% 0.00% sh 5912 nagios 40 120K 680K STOP 0:00 0.00% 0.00% ping 12175 nagios 20 2500K 932K STOP 0:00 0.00% 0.00% nagios 8571 nagios 20 228K 724K STOP 0:00 0.00% 0.00% check_ping no this still hangs. on ping 127.0.0.1 oddly enough. (im using some of the provided sample configs) I added printfs to command.c to see which fork()/waitpid() hangs, but afaik never actualy logs anything anywhere, i will have to start over creating a new file handle, or maybe print to stderr ? Spent a few hours googling the other day for hang nagios STOP, WAIT etc, and never got any resolution. to make matters worse many sites now dont publish whole email addresses, so its hard to contact anyone whose had this problem before and get resolution. On Sat, 7 Jan 2006, Hugo van der Kooij wrote: Date: Sat, 7 Jan 2006 11:16:54 +0100 (CET) From: Hugo van der Kooij [EMAIL PROTECTED] To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] ping hanging. On Sat, 7 Jan 2006, Hugo van der Kooij wrote: And 4400:34 may be valid syntax for a IPv6 address. Should read 4400::34 and not 4400:34 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=7637alloc_id=16865op=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 Microsoft: Where do you want to go tomorrow? Linux: Where do you want to go today? BSD: Are you guys coming, or what? Robin-David Hammond KB3IEN www.aresnyc.org. --- 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=7637alloc_id=16865op=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] ping hanging.
As for 4400::34 It is not a darpa net IP, but the host ip is valid on this host. In this case the libexec directory had been deleted, possibly by me, possibly not. re `make install`ing the plugs seems to have worked. I too need this caffeine level indicator. I hope it will support HTCPCP. I am not now attemtping to determine if the ping lock problem persists. (this problem was also noticed with IPv4 hosts, ampr and darpa, both routed and RFC1918.) On Sat, 7 Jan 2006, Hugo van der Kooij wrote: Date: Sat, 7 Jan 2006 11:11:55 +0100 (CET) From: Hugo van der Kooij [EMAIL PROTECTED] Reply-To: nagios-users@lists.sourceforge.net To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] ping hanging. On Sat, 7 Jan 2006, Hammond, Robin-David%KB3IEN wrote: In order to try to diagnose the nagios problem whereby it enteres the wait state indefinitely, i added some debugging code to commands.c, and rebuilt nagios 2.0rc1. I am now getting a very strange error /Warning: Attempting to execute the command /check_ping -H 4400::34 -w 3000.0,80% -c 5000.0,100% -p 1 -t 10 -6 resulted in a return code of 127. Make sure the script or binary you are trying to execute actually exists... If check_ping calls the normal ping utility you will need to rewrite it for IPv6. Your normal ping will not handle IPv6 addresses. That will be the job of ping6 on most systems. And 4400:34 may be valid syntax for a IPv6 address. But to the best of my knowledge it is not a valid IPv6 address. Valid ranges will be 2000:: untill 3fff:: for public addreses and fe80:: and upwards for link-local addresses. And check_host does work on IPv6 addresses as I have several IPv6 only systems in my setup which I can contact just fine. A manual test here: ./check_ping -H 2001:888:10fa:1 -w 100,20% -c 500,50% check_ping: Invalid hostname/address - 2001:888:10fa:1 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=7637alloc_id=16865op=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 Microsoft: Where do you want to go tomorrow? Linux: Where do you want to go today? BSD: Are you guys coming, or what? Robin-David Hammond KB3IEN www.aresnyc.org. --- 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=7637alloc_id=16865op=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] ping hanging.
-Original Message- From: [EMAIL PROTECTED] [mailto:nagios-users- [EMAIL PROTECTED] On Behalf Of Hammond, Robin-David%KB3IEN Sent: Friday, January 06, 2006 10:02 PM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] ping hanging. In order to try to diagnose the nagios problem whereby it enteres the wait state indefinitely, i added some debugging code to commands.c, and rebuilt nagios 2.0rc1. I am now getting a very strange error /Warning: Attempting to execute the command /check_ping -H 4400::34 -w 3000.0,80% -c 5000.0,100% -p 1 -t 10 -6 resulted in a return code of 127. Make sure the script or binary you are trying to execute actually exists... over and over. this is particularly confusiong as i never reran configure nor did I ever uninstall the /check_ping programme it is still in place and executable. Any ideas? Return code 127 means that the plugin was not found in the location specified in the command definition. Nagios is apparently trying to execute /check_ping and not /path/to/check_ping (usually /usr/local/nagios/libexec/check_ping). There are four primary possibilities -- 1) your command definition does not utilize the $USER1$ macro in the command_line i.e. 'command_line $USER1$/check_ping -H ...' 2) you have manually specified the incorrect path in the command_line i.e. 'command line /check_ping -H ...' 3) $USER1$ is not set to the correct plugins path in resource.cfg 4) you have not included resource.cfg as a resource_file in nagios.cfg -- Marc --- 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_idv37alloc_id865op=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
