I had one of the techs pull up the error and we believe this is it [Error: The current connection has been aborted by the network or intermediate services.]
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Friday, November 09, 2007 2:25 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Strange SA IIS hang? "SA would stop doing checks altogether and report everything as down." => what does SA then give as reason for the down? ProcessID 1960 was that Servers ALive or IIS? Dirk Bulinckx. From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dolinar, Jon Sent: Friday, November 09, 2007 8:16 PM To: Servers Alive Discussion List Subject: [SA-list] Strange SA IIS hang? Since going to version 6.1.2165 I am now using 2171 I have been having a problem that follows the following symptoms. A little background SA is running on Windows 2003 server as a service. IIS is also installed on the same server and SA is writing the webpage output to the local drive. About every 24+ hours the webpage for SA would return page not found after a few hours of this SA would stop doing checks altogether and report everything as down. If I restart the SA service when the page is not found everything goes back to normal. If I wait till the checks return all down I have to reboot the machine. After much tracing this down I found the following. When web page stops displaying the following event shows in the event log: A worker process with process id of '1960' serving application pool 'DefaultAppPool' has requested a recycle because the worker process reached its allowed processing time limit. Turns out that the IIS default application pool is set to recycle the worker process every 1740 minutes or 29 hours. When this happens SA must be restarted? Strange thing is that the other SA box which only does ping checks and snmp queries and one URL check this does not happen on. Any thoughts? 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.
