Nagios check_ping times

[Reg]

check_fping reduced the overall overhead.  I also made a ramdisk for the 
status file.  Much better overall ping times.  I think the status file 
on ramdisk was the silver bullet.  Tried fping first and found it still 
reported high latency.  I suspect vmware is a little slow in writing to 
the disk - although that doesn't seem to be a problem with the database 
servers we have running there.


Marc Powell wrote:


>  
>
>>-----Original Message-----
>>From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
>>admin at lists.sourceforge.net] On Behalf Of Reg
>>Sent: Tuesday, January 10, 2006 11:19 PM
>>To: nagios-users at lists.sourceforge.net
>>Subject: [Nagios-users] Nagios check_ping times
>>
>>I sporadically ( 1 or 2 times/day for 50 hosts) get check_ping
>>    
>>
>returing
>  
>
>>average response times of 500ms plus resulting in false "critical"
>>alerts from Nagios.  E.G.
>>PING CRITICAL - Packet loss = 0%, RTA = 535.87 ms
>>
>>I'm running Suse 9.1 on VMWare ESX server.  I DO NOT believe vmware to
>>be a factor because I also run smokeping on this virtual machine.
>>SmokePing sends 3 pings every 5 seconds to the same hosts and never
>>shows the 500ms+ latency that Nagios reports.  During the course of a
>>typical day I get 80-100 of these "false alarms"
>>I suspect the problem is in the nagios daemon and how i have it
>>configured.  When i run check_ping manually i can't reproduce the
>>500ms+.  Are there any quick tests or diagnostics to help figure
>>    
>>
>what's
>  
>
>>going on?
>>    
>>
>
>I have personally seen discrepancies between the results of fping tests
>(which Smokeping uses) and ping tests (which check_ping uses), even to
>the point where one works and the other doesn't. Though that last case
>turned out to be a circuit issue, you might want to try using
>check_fping to see if your problems go away. I can't imagine any
>configuration that you could implement that would cause ping to falsely
>report high latencies. 
>
>Another thing you might want to check is the load on the server at those
>times. If the load is abnormally high it might delay ping's processing
>of the return results.
>
>--
>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_idv37&alloc_id865&op=click
>_______________________________________________
>Nagios-users mailing list
>Nagios-users at 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users at 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