Packet loss reported by check_ping?

Andreas Ericsson ae at op5.se
Wed Dec 13 16:50:02 CET 2006


I would appreciate if you didn't bring mail discussions off-list. It 
prevents others who might have the same problem from benefiting from the 
suggestions, and makes it impossible for archivers to pick up the entire 
discussion which in turn makes it impossible for google to index it, so 
that means everyone on this list that answers questions will have to 
answer the same question over and over again.

Please don't do it again. Thanks.

Andy Shellam (Mailing Lists) wrote:
> Andreas,
>>> Also, along those lines...  I recently moved from the 1.2 Nagios to 
>>> the more recent 2.4-2.5 Nagios.  Nagios 1.X seemed to only trigger a 
>>> host check if a service check failed.  Nagios 2.X seems to ALWAYS run 
>>> host checks in addition to service checks.  The fact that host checks 
>>> are currently not run in parallel seems like this can really limit 
>>> performance.
>>>
>>> Why did that behavior change?
>>>     
>>
>> It didn't. Or rather, it wasn't supposed to. I haven't seen anything 
>> of the kind in any of our ~160 customers installations, so I'm fairly 
>> certain this doesn't happen for all setups. What does your nagios.log 
>> report on the ~15 lines prepending the host-check entry?
>>   
> 
> 
> [1165968000] LOG ROTATION: DAILY
> [1165968000] LOG VERSION: 2.0
> [1165968000] CURRENT HOST STATE: Cairns;UP;HARD;1;PING OK - Packet loss 
> = 0%, RTA = 0.93 ms
> [1165968000] CURRENT HOST STATE: FH-Gateway;UP;HARD;1;PING OK - Packet 
> loss = 0%, RTA = 0.19 ms
> [1165968000] CURRENT HOST STATE: Perth;UP;HARD;1;PING OK - Packet loss = 
> 0%, RTA = 0.08 ms
> [1165968000] CURRENT HOST STATE: SC-Gateway;UP;HARD;1;PING OK - Packet 
> loss = 0%, RTA = 5.89 ms
> [1165968000] CURRENT HOST STATE: Sydney-1;UP;HARD;1;PING OK - Packet 
> loss = 0%, RTA = 6.62 ms
> [1165968000] CURRENT HOST STATE: Sydney-2;UP;HARD;1;PING OK - Packet 
> loss = 9%, RTA = 9.10 ms
> [1165968000] CURRENT SERVICE STATE: Cairns;- OVERALL SERVER 
> AVAILABILITY;OK;HARD;1;PING OK - Packet loss = 0%, RTA = 1.15 ms
> ---- the above line is repeated for every host/service combination ----
> [1165968024] Warning: The results of host 'Cairns' are stale by 45 
> seconds (threshold=15 seconds).  I'm forcing an immediate check of the 
> host.
> ---- the above line is repeated for every host ----
> 
> The "stale by xx seconds" varies between 40 and 70 seconds.
> 

I'm guessing you've enabled passive host checks and also enabled 
freshness checking with a freshness threshold for hosts. This will 
effectively force host-checks with exactly the sort of logmessages you 
showed above.

> However in Nagios' front-end, scheduled hosts checks are apparently 
> disabled:
> 
> Last Check Type:     ACTIVE
> Last Check Time:     13-12-2006 15:19:18
> Status Data Age:     0d 0h 0m 59s
> Next Scheduled Active Check:       N/A
> 

Yes, the checks aren't scheduled the normal way, or you wouldn't see the 
"warning... stale by...". It would just run the check and shut up.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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





More information about the Users mailing list