forums.meulie.net

Something odd with Check_Ping

this is log file of nagios.log

[1116601120] Warning: Return code of 139 for check of service ‘PING’ on host ‘res-yoda-01’ was out of bounds.
[1116601124] SERVICE ALERT: res-yoda-01;PING;CRITICAL;SOFT;1;(Return code of 139 is out of bounds)
[1116601180] Warning: Return code of 139 for check of service ‘PING’ on host ‘res-yoda-01’ was out of bounds.
[1116601184] SERVICE ALERT: res-yoda-01;PING;CRITICAL;SOFT;2;(Return code of 139 is out of bounds)
[1116601240] Warning: Return code of 139 for check of service ‘PING’ on host ‘res-yoda-01’ was out of bounds.
[1116601245] SERVICE ALERT: res-yoda-01;PING;CRITICAL;SOFT;3;(Return code of 139 is out of bounds)
[1116601300] Warning: Return code of 139 for check of service ‘PING’ on host ‘res-yoda-01’ was out of bounds.
[1116601310] HOST ALERT: res-yoda-01;DOWN;SOFT;1;Segmentation fault
[1116601311] HOST ALERT: res-yoda-01;UP;SOFT;2;PING OK - Packet loss = 0%, RTA = 0.04 ms
[1116601311] SERVICE ALERT: res-yoda-01;PING;CRITICAL;HARD;4;(Return code of 139 is out of bounds)

config
define service{
use generic-service ; Name of service template to use
host_name res-yoda-01
service_description PING
is_volatile 0
check_period 24x7
max_check_attempts 4
normal_check_interval 5
retry_check_interval 1
contact_groups admins
notification_interval 960
notification_period 24x7
check_command check_ping!100.0,20%!500.0,60%
}

Checkcommands

‘check_ping’ command definition

define command{
command_name check_ping
command_line $USER1$/check_ping -H $HOSTADDRESS$ -w $ARG1$ -c $ARG2$ -p 2
}

Do a ls -la on your /usr/local/nagios directory and also one on the /usr/local/nagios/libexec and paste the output here.
The error message is telling you that the file does not exist, is one possibility, which indicates that you have incorrect permissions.

Also paste your entry in resource.cfg for the entry
$USER1$=???
and verify that it points to the correct directory of your plugin location.

I’ll grab those, but all other plugins are working fine that I have configured, check load, check proccess, check users, check http, check disk (3 diffrent partitions).

Also odd thing with ping, it works sometimes, probably 1 out of 4, the rest fail. Sometimes its green on the web application then rest its the error of 139.

total 44
drwxr-xr-x 10 www www 512 May 19 10:00 .
drwxr-xr-x 26 root wheel 512 May 19 13:43 …
-rwxr-xr-x 1 www www 117 May 19 10:05 .htaccess
drwxr-xr-x 2 www www 512 May 19 10:33 cgi-bin
drwxr-xr-x 2 www www 1536 May 18 13:54 contexthelp
drwxr-xr-x 3 www www 1536 May 18 13:54 docs
drwxr-xr-x 3 www www 1536 May 18 13:54 images
-rw-r–r-- 1 www www 658 May 18 13:54 index.html
drwxr-xr-x 4 www www 512 May 18 13:32 locale
-rw-r–r-- 1 www www 2341 May 18 13:54 main.html
drwxr-xr-x 2 www www 512 May 18 13:54 media
-rw-r–r-- 1 www www 26 May 18 13:54 robots.txt
-rw-r–r-- 1 www www 12729 May 18 13:54 side.html
drwxr-xr-x 2 www www 512 May 18 13:54 ssi
drwxr-xr-x 2 www www 512 May 18 13:54 stylesheets

yoda# ls -la
total 948
drwxr-xr-x 2 nagios nagios 1536 May 20 09:23 .
drwxr-xr-x 8 root wheel 512 May 18 13:32 …
-r-xr-xr-x 1 nagios nagios 2260 May 18 13:32 check_breeze
-r-xr-xr-x 1 nagios nagios 25376 May 18 13:32 check_by_ssh
-r-xr-xr-x 1 nagios nagios 23972 May 18 13:32 check_dhcp
-r-xr-xr-x 1 nagios nagios 23408 May 18 13:32 check_dig
-r-xr-xr-x 1 nagios nagios 28056 May 18 13:32 check_disk
-r-xr-xr-x 1 nagios nagios 8029 May 18 13:32 check_disk_smb
-r-xr-xr-x 1 nagios nagios 27904 May 18 13:32 check_dns
-r-xr-xr-x 1 nagios nagios 8712 May 18 13:32 check_dummy
-r-xr-xr-x 1 nagios nagios 3075 May 18 13:32 check_file_age
-r-xr-xr-x 1 nagios nagios 6380 May 18 13:32 check_flexlm
lrwxr-xr-x 1 root wheel 9 May 18 13:32 check_ftp -> check_tcp
-r-xr-xr-x 1 nagios nagios 22688 May 18 13:32 check_hpjd
-r-xr-xr-x 1 nagios nagios 42908 May 18 13:32 check_http
-r-xr-xr-x 1 nagios nagios 18220 May 18 13:32 check_icmp
-r-xr-xr-x 1 nagios nagios 15272 May 18 13:32 check_ifoperstatus
-r-xr-xr-x 1 nagios nagios 12838 May 18 13:32 check_ifstatus
lrwxr-xr-x 1 root wheel 9 May 18 13:32 check_imap -> check_tcp
-r-xr-xr-x 1 nagios nagios 7436 May 18 13:32 check_ircd
lrwxr-xr-x 1 root wheel 9 May 18 13:32 check_jabber -> check_tcp
lrwxr-xr-x 1 root wheel 10 May 18 13:32 check_ldaps -> check_ldap
-r-xr-xr-x 1 nagios nagios 19820 May 18 13:32 check_load
-r-xr-xr-x 1 nagios nagios 5971 May 18 13:32 check_log
-r-xr-xr-x 1 nagios nagios 20730 May 18 13:32 check_mailq
-r-xr-xr-x 1 nagios nagios 18508 May 18 13:32 check_mrtg
-r-xr-xr-x 1 nagios nagios 16860 May 18 13:32 check_mrtgtraf
-r-xr-xr-x 1 nagios nagios 19524 May 18 13:32 check_nagios
lrwxr-xr-x 1 root wheel 9 May 18 13:32 check_nntp -> check_tcp
lrwxr-xr-x 1 root wheel 9 May 18 13:32 check_nntps -> check_tcp
-r-xr-xr-x 1 nagios nagios 26748 May 18 13:32 check_nt
-r-xr-xr-x 1 nagios nagios 13265 May 18 13:32 check_ntp
-r-xr-xr-x 1 nagios nagios 30848 May 18 13:32 check_nwstat
-r-xr-xr-x 1 nagios nagios 8293 May 18 13:32 check_oracle
-r-xr-xr-x 1 nagios nagios 22652 May 18 13:32 check_overcr
-r-xr-xr-x 1 nagios nagios 20380 May 18 13:32 check_pgsql
-r-xr-xr-x 1 nagios nagios 27248 May 18 13:32 check_ping
lrwxr-xr-x 1 root wheel 9 May 18 13:32 check_pop -> check_tcp
-r-xr-xr-x 1 nagios nagios 26940 May 18 13:32 check_procs
-r-xr-xr-x 1 nagios nagios 19976 May 18 13:32 check_radius
-r-xr-xr-x 1 nagios nagios 20772 May 18 13:32 check_real
-r-xr-xr-x 1 nagios nagios 9692 May 18 13:32 check_rpc
-r-xr-xr-x 1 nagios nagios 1176 May 18 13:32 check_sensors
lrwxr-xr-x 1 root wheel 9 May 18 13:32 check_simap -> check_tcp
-r-xr-xr-x 1 nagios nagios 25724 May 18 13:32 check_smtp
-r-xr-xr-x 1 nagios nagios 30844 May 18 13:32 check_snmp
lrwxr-xr-x 1 root wheel 9 May 18 13:32 check_spop -> check_tcp
-r-xr-xr-x 1 nagios nagios 18556 May 18 13:32 check_ssh
-r-xr-xr-x 1 nagios nagios 21072 May 18 13:32 check_swap
-r-xr-xr-x 1 nagios nagios 27652 May 18 13:32 check_tcp
-r-xr-xr-x 1 nagios nagios 19944 May 18 13:32 check_time
-r-xr-xr-x 1 nagios nagios 19020 May 18 13:32 check_udp
lrwxr-xr-x 1 root wheel 9 May 18 13:32 check_udp2 -> check_tcp
-r-xr-xr-x 1 nagios nagios 24916 May 18 13:32 check_ups
-r-xr-xr-x 1 nagios nagios 18508 May 18 13:32 check_users
-r-xr-xr-x 1 nagios nagios 3004 May 18 13:32 check_wave
-r-xr-xr-x 1 nagios nagios 18500 May 18 13:32 negate
-r-xr-xr-x 1 nagios nagios 31796 May 20 09:23 nsca
-r-xr-xr-x 1 nagios nagios 20244 May 20 09:23 send_nsca
-r-xr-xr-x 1 nagios nagios 17532 May 18 13:32 urlize
-r-xr-xr-x 1 nagios nagios 2449 May 18 13:32 utils.pm
-r-xr-xr-x 1 nagios nagios 876 May 18 13:32 utils.sh

Sets $USER1$ to be the path to the plugins

$USER1$=/usr/local/libexec/nagios

Sets $USER2$ to be the path to event handlers

#$USER2$=/usr/local/libexec/nagios/eventhandlers
also question,
User2, doesnt exsist, anywhere on my system.

" $USER1$=/usr/local/libexec/nagios "
Nagios by default is in /usr/local/nagios.
libexec is normally
/usr/local/nagios/libexec
your plugins should be in /usr/local/nagios/libexec.

I think you have installed to the wrong directory, so we as a group, are going to have a hard time working with you, since you chose to install someplace else. Can you explain why this was needed?

I installed nagios from the ports on freebsd, it placed everything there

nagios is in /usr/local/sbin/nagios

/usr/local/libexec/nagios/ is plugins

and /usr/local/etc/nagios/ is config files

/usr/local/share/nagios is where the cgi, html ect is stored.

I can handle checking the paths and such, I’m not a complete noobie to freebsd, but Nagios I’ll proudly wear the noob hat :smiley:
Edited Fri May 20 2005, 08:43AM ]

Then by the sounds of it, you didn’t compile on this box, which may just be why the plugin is acting so screwy. Try removing the precompiled rpm package, or whatever and install from source code.

Did you fix this? By the sounds of your other thread, you did, but we don’t know what you did to fix it. Please share your toys.

still havent fixed it, but I think I tracked it down, err code 139 is a dos attack. Freebsd has features built in to automatically protect itself from being dosed. I think the command works for the first few times, then the box thinks its being dos’d and starts returning error codes. I’ll research it more later since I need to get other services working on remote boxes.

Will provide more info as I get it.

jakkedup: quick FYI-

With the FreeBSD ports, the program is compiled from source. Typically the user changes into the ports directory, finds the port that they want to install and type in ‘Make’. The machine then goes out to the 'net and finds a tarball to download and install from.

next item: I am also having issues with check_ping giving me segmentaion faults. I recently upgraded from nagios 1.2 to the 2.0b3. I brought the 2.0b3 up around 11:00 mst yesterday and got my first seg fault message at 17:25 mst.

agamemnon: what updates do you have for us? I am also running on a FreeBSD box

in /var/log/messages I see a lot of these
May 24 13:37:03 yoda kernel: pid 8261 (check_ping), uid 1004: exited on signal 11

looks like ping is crashing a lot, still no resolution, but still debuging :slight_smile:

Did anyone ever come up with a resolve for this? Usually if the FreeBSD DDoS protection would come in to effect, we would see an ICMP limit message in /var/log/messages but none. It just started on our system after running successfully for many months. We upgraded to 2.0b6 a few weeks ago, using FreeBSD ports.

Sounds like this is a firewall problem then and not nagios at all. Try disabling your firewall and find out.

On freebsd, you might have a look at sysctl.conf:

net.inet.icmp.icmplim=200 (reduces the effect of a ICMP DoS attack)

-mike

I also thought it might be “icmplim” I used “ping -f” both from the host outbound and also ran “ping -f” from another node to flood my nagios node, I have done this for a good few min, but still no error (In the log it displays the limiting).
I have now given up on trying on resolving this. It is totally intermittent. It does not affect my notifications since the 2de check will be ok. Sometimes it does not happen for weeks.

Interesting