IIS 5 & IIS 6
IIS Reset Daily to keep website active
Last post Jul 28, 2008 03:31 PM by kberling
Jul 28, 2008 12:54 PM|kberling|LINK
After a given period of time I have to execute an IIS reset to fix an intermittent problem. Our webserver is co-located at an outside facility. Not seeing anything in the system logs or IIS logs to clue me in.
What's happening is occasionally I try to access our website and the page just times out but if I try another computer in my same office I can access the site just fine. At random any computer is unable to access our site while others can. After about 5
minutes the computer that can't access the site is now able to. An IIS reset fixes the problem right away but it's just a temporary fix. We are running IIS6 with Windows Server 2003 SP2.
Any suggestions on permanent fixes?
Jul 28, 2008 02:26 PM|Rovastar|LINK
When it 'goes wrong' what is happening on the server?
Is anything in the IIS logs? Do your request from a failing machine (look by IP address) get as far as this? If so what is it say http status, sub status, win32 error, time taken, bytes, etc.
look in the httperr logs too.
Any otehr long running pages at the time.
Wgat is the CPU/memory usage like for this app pool?
It is probably a code issue.
But failing all that debugdiag can probably help.
Jul 28, 2008 02:38 PM|kberling|LINK
Thanks for your reply. I don't see anything unusual in the IIS logs. I looked for the IP from the failing machine but doesn't get this far. I have a lot of entries in the httperr logs for Timer_ConnectionIdle but those should be normal.
CPU/memory usage should be nil. We have 16GB of memory and 4 quad core processors on a machine that is barely utilized.
The strangest part is that the site continues to run. I can connect multiple times with different clients during the time I'm unable to connect with 1 client. If the site were down I wouldn't be able to connect from any client.
I'm not seeing any clues in the logs.
Jul 28, 2008 02:47 PM|Rovastar|LINK
So are your requests (from the machine that cannot connect) recorded in the IIS logs or not?
If so what are they?
Jul 28, 2008 03:02 PM|kberling|LINK
No, the failed requests are not recorded. I wish they were, that would help.
Jul 28, 2008 03:15 PM|Rovastar|LINK
Although you have a lot of memory in the machine what is the actual worker process (w3wp.exe) for that application pool doing?
What errors do the clients see? turn off show friendly error messages on the erroring client machines.
I would also look at installing a network monitor app like netmon on the server/network to see if you can determine if the requests are even getting to the server.
Is there a lot of traffic on the site? I presume not but thought I would ask.
Does clearing the caches, etc on the client machines help when you have this problem.?
What technologies is the site using asp.net, php, etc
Jul 28, 2008 03:31 PM|kberling|LINK
The w3wp.exe service is running around 107,000K currently.
I'm disabling friendly errors now so the next time it happens I'll see if I get a real error message.
I don't believe clearing the cache helps but I will try that.
We are using asp.net and also running SQL 2005. That's about it.
Not much traffic. Only a handful of users at this time.
Thank you so much for continuing to help.