Discussion Locked

inetinfo.exe takes 100% of cpu

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have clustered Dual PIII Xeon 500Mhz servers with 512Mb RAM, running NT4 SP6a & IIS4.
From time to time inetinfo.exe will take 50% of CPU resource (effectively hogging one of the dual cpu's completely). At this point, the websites hang.
We can take the W3SVC offline, but cannot stop IIS Admin service, it thinks W3SVC is still running. Cannot kill inetinfo in taskmanager either. The only way for us to recover is to fail-over and reboot the server.
Anyone else had this problem, and did u find what was causing the problem?

5 replies

by curacao_dejavu

Check out the MS KB Article ID: Q253603HOWTO: Troubleshoot a High-CPU-Utilization "Hang" in Internet Information Services

Also do you have the patches installed for IIS 4 (especially the security ones).

On the resource kit there is a called kill.exe which allows to to "kill" a app, so you wont need to restart any more.
You can try also the "net start" and "net stop" command, (net start /? for help) maybe that can help also.

Leopold

by curious_george

There are 4 types of MS clustering, you do not mention which one, however since you mention the word "failover" I assume you mean MSCS.

2 quicks ideas:
1. The video hooks in remote control applications often produce these results, if you are running any try disabling them for a while.

2. Are you running MTS on your web servers, often the log files get quite large and produce high CPU utilization. Stop MTS, Copy the log to a new location or rename, and then restart MTS.

Also make sure you have all your hot-fixes in place, malicious attacks can cause IIS to loop exceessively.

by curious_george

One last note: the kill executable, the kill.vbs and the sc.exe files in the resource kit, as well as the net stop/start commands, almost surely use the same APIs, so if it won't stop with a local call, it is very unlikely it will stop with an RPC.

This discussion is closed to new replies.