The Windows OS is so "great" that some of the API calls that are part of it don't respect their own timeout settings. That's why you get this behaviour. Typicaly authentication can take that long (300 seconds) and the only thing that we could do about it is, is run this is a different thread and kill the thread IF it's taking too long BUT this means that automaticly you create a resource leak and that is something that is NOT OK to have.
Dirk Bulinckx. From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, December 10, 2008 11:16 AM To: Servers Alive Discussion List Subject: [SA-list] Long timeouts for certain Windows related errors I have diskspace checks configured for a server at a remote site. We're have some problems with that site (don't know yet if it's the server, the network or something else) which result in attempts to contact that server (by SA or by anything else) failing. SA gives a "specified network name is no longer available" error in the log. Clearly that isn't SA's problem. However, when SA hits that check it sits on it for up to 300 seconds (!) rather than timing out after 5 seconds as configured in the check. Is there something that can be done about that? (The problem is a real pain as there are actually two checks configured for that server, and both have second-knock configured. That means a potential delay of 20 minutes per check cycle - as against a normal check cycle of about 1 minute!) Cheers, Ian _________________________________ Ian K Gray OEL IS - European Infrastructure Support Tel: +44 1236 502661 Mob: +44 7881 518854 Ad eundum quo nemo ante iit ______________________________________________________________________________ Any opinions expressed in this email are those of the individual and not necessarily of the Company. This email and any files transmitted with it, including replies and forwarded copies (which may contain alterations) subsequently transmitted from the Company are confidential and solely for the use of the intended recipient. It may contain material protected by legal privilege. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this email in error and that any use is strictly prohibited. Please notify the sender immediately of the error and delete any copies of this message Warning: Although the Company has taken reasonable precautions to ensure that no viruses are present in this e-mail, the Company cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
