Gerry, That's very similar to what I'm seeing for this one check - except that (perversely) we were on 2053, but it's started to behave as you describe now that we've upgraded to 2072. I increased the timeout from 5 to 10 seconds a few hours ago - no failures yet.
Ian _________________________________ Ian K Gray OEL IS - European Infrastructure Support Tel: +44 1236 502661 Mob: +44 7881 518854 "Gerry Aquino" <[EMAIL PROTECTED]> Sent by: Servers Alive Discussion List <[email protected]> 15/12/2006 14:35 Please respond to Servers Alive Discussion List <[email protected]> To Servers Alive Discussion List <[email protected]> cc Subject Re: [SA-list] Timeouts This may or may not be relevant, but ever since upgrading to v6 (currently on 6.0.2053) from v5, many checks that rarely timed now time out regularly. The checks most affected for me seem to be DNS checks and URL checks. Most timeouts are set to 5 seconds. Usual DNS queries take less than 200ms but often fail the 5 seconds timeout. Doing a manual check from the GUI immediately after a fail will succeed with the usual <200ms time. The same thing happens with some URL checks, they will fail with a timeout, but can immediately be manually checked and pass. Enabling second knock has helped this a lot, but some checks will still fail the SK, but succeed when manualy checked. BTW, whenthey fail they usually have received NO data per the logs. The system SA runs on is a PIII 1Ghz 256M Optiplex 150. This box is only running SA and VNC plus normal Win2k Pro services and has not had any changes to it from v5 to v6. Check number 100, mostly DNS and URL. The only change I have made that seemed to improve this situation was to turn off the Virus scanning component of NOD32 that scans all incoming Internet traffic. This was, however, always on with v5. Not sure if that helps or is relevant, but just my observations as i try to figure out why this is happening. Gerry On 12/15/06, [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) <[EMAIL PROTECTED] (mailto:[EMAIL PROTECTED])> wrote: A further timeout problem (albeit different to yesterday's one) - we do an NT Perfmon check on committed memory on one server. It normally returns a value in about 350ms. Since yesterday, that has timed out 6 times (timeout set to 5 seconds, second knock enabled). Any ideas what might be casuing this? Ian _________________________________ Ian K Gray OEL IS - European Infrastructure Support Tel: +44 1236 502661 Mob: +44 7881 518854 To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] (mailto:[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. -- Gerry Aquino 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.
