And what timeout did you set on that check? Dirk Bulinckx.
-------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 14, 2006 3:16 PM To: Servers Alive Discussion List Subject: Fw: [SA-list] Ping stats not correct: FIXED One strange thing: since installing this beta (and bear in mind that I've moved from build 2057), the cycle time has nearly doubled. Looking at it, I suspect that this is due to an external com check (checking an event log across a 4Mb WAN link) which is now taking 4 or 5 minutes. It's threaded, but nevertheless it's still going for 3 or 4 minutes after everything else. Any ideas? Ian _________________________________ Ian K Gray OEL IS - European Infrastructure Support Tel: +44 1236 502661 Mob: +44 7881 518854 ----- Forwarded by Ian Gray/OEL/OKI_DATA_CORP/OKI_ELECTRIC/US on 14/12/2006 14:09 ----- Ian Gray/OEL/OKI_DATA_CORP/OKI_ELECTRIC/US 14/12/2006 12:24 To Servers Alive Discussion List <[email protected]> cc Subject RE: [SA-list] Ping stats not correct: FIXEDLink (Notes:///80256BAA003E2058/DABA975B9FB113EB852564B5001283EA/FF47CBE0FA8955ED802572440040CA12) Excellent, appears to be working. Thanks Dirk! I'm sure you've told me before but I can't remember the answer: is the uptime percentage since the last stop/start, or since the program started, or what? Cheers, Ian _________________________________ Ian K Gray OEL IS - European Infrastructure Support Tel: +44 1236 502661 Mob: +44 7881 518854 "Dirk Bulinckx" <[EMAIL PROTECTED]> Sent by: Servers Alive Discussion List <[email protected]> 14/12/2006 11:45 Please respond to Servers Alive Discussion List <[email protected]> To Servers Alive Discussion List <[email protected]> cc Subject RE: [SA-list] Ping stats not correct: FIXED On http://beta.woodstone.nu (http://beta.woodstone.nu/) there is an updated build (6.1.2072) that fixes the issue. Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Thursday, December 14, 2006 12:06 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Ping stats not correct Perfect! That was it, it seems to do this only when something else is depending on it. (even from the first cycle on). At least now I can start searching/debugging... Thanks. Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 14, 2006 12:01 PM To: Servers Alive Discussion List Subject: Re: [SA-list] Ping stats not correct Dirk, We see this from the<sa_stats_uptime> tag. It's not happening with all pings - the common factor appears to be that it happens when a ping check has one or more other checks dependent on it. For example, if a server is just pinged, it gives 100% uptime. But if it gets pinged and then (assuming the ping happens) we check an NT service or diskspace or something, the original ping gives a 200% uptime. All pings have SK enabled. Will check how quickly it does it presently... Cheers, Ian _________________________________ Ian K Gray OEL IS - European Infrastructure Support Tel: +44 1236 502661 Mob: +44 7881 518854 "Dirk Bulinckx" <[EMAIL PROTECTED]> Sent by: Servers Alive Discussion List <[email protected]> 14/12/2006 10:20 Please respond to Servers Alive Discussion List <[email protected]> To Servers Alive Discussion List <[email protected]> cc Subject [SA-list] Ping stats not correct I already got 2 people telling me that the uptime stats of a ping check were giving wrong results (200% uptime :-)), unfortunatly I'm not able to reproduce the problem. So if you're having this problem too, can you tell me HOW you see this uptime (html output? If so what tag, or ...) and is this for all pings checks or only for some of the ping checks? And do these ping checks have SK enabled? Does it do this directly (from the first cycle already) or only after a few cycles? (if you add a new ping check does it have the problem then too). Well all info that seems relevant in order to reproduce the problem. Dirk Bulinckx. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
