ping and ping6

[nagarjuna]

We have configured NRDS agent for passive checks on thousands of machines, we are getting this error only on some of 30-40 clients only.

As you asked please check the following:

root@host [~]# ping google.com
PING google.com (173.194.36.38) 56(84) bytes of data.
64 bytes from bom04s02-in-f6.1e100.net (173.194.36.38): icmp_seq=1 ttl=57 time=14.3 ms
64 bytes from bom04s02-in-f6.1e100.net (173.194.36.38): icmp_seq=2 ttl=57 time=14.6 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1391ms
rtt min/avg/max/mdev = 14.366/14.495/14.625/0.176 ms

root@host [~]# ifconfig
em1 Link encap:Ethernet HWaddr B8:AC:6F:99:10:26
inet addr:182.18.128.219 Bcast:182.18.128.255 Mask:255.255.255.0
inet6 addr: 24001:2:baac:6fff:fe99:1026/64 Scope:Global
inet6 addr: fe80::baac:6fff:fe99:1026/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:277009289 errors:0 dropped:0 overruns:0 frame:0
TX packets:20667295 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:36194486933 (33.7 GiB) TX bytes:19086978936 (17.7 GiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1446431 errors:0 dropped:0 overruns:0 frame:0
TX packets:1446431 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2646535666 (2.4 GiB) TX bytes:2646535666 (2.4 GiB)

root@host [~]#

[tmcdonald]

If the clients having the issues have em1 as the interface and those that are working have eth0 or eth1 as the interface name, I want you to try what's in the following post:

http://www.sysarchitects.com/em1_to_eth0

Read through it first and consult with the admins of those servers to make sure this won't break any custom scripts.

[nagarjuna]

Hi tmcdonald,

It will help me a lot, may be it will resolve my whole issue, i will check and get back to you definitely. Thanks

[slansing]

Awesome, let us know as it is the likely solution!

[nagarjuna]

Hi Team,

We cant change interface in client machines, they are not allowed to change the interface name on their system.

As i seen today, we are getting this ping and ping6 error messages, which client machines are flapping also. and disabled flapping and issue seems resolved.

Enable flapping then
/bin/ping6 -n -U -w 10 -c 1 localhost


Disable flapping then
Up
PING OK - Packet loss = 0%, RTA = 0.03 ms

Please confirm is it ok? or some thing we missed if we are doing this?

[sreinhardt]

Disabling flapping is just fine, although it may lead to more false positives. It also should not really effect the results of your checks, just whether nagios detects false positives for intermittent checks not running properly.

[nagarjuna]

I am getting this in /var/log/messages for all hosts,

nagios: HOST NOTIFICATION: nagiosadmin;ebillingsolutions-xxx.xxx.xxx.xxx;DOWN;xi_host_notification_handler;/bin/ping6 -n -U -w 10 -c 1 localhost
..
..
..
..

Should we changed something in xi_host_notification_handler?

[slansing]

I'm not quite sure what prompted that question, nagios is sending out a notification in that snippet, or attempting to.

[nagarjuna]

Hi Slansing,

Thanks for your attention on it.
Finally i got resolved, this issue with remote linux box(all centos systems).

# chmod u+s /bin/ping
# chmod u+s /bin/ping6

and thats it. its working as a charm. thanx


You can close this issue..........