• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Problems with NT server, crashes/slowdowns

archimedian

Junior Member
Hi, I'm moving this here because I think it fits the forum better.

I am having a problem with NT server. We run a server that serves over 100 different web sites and gets a fair amount of traffic (I would guess that we serve somewhere around 5 million page views per month). The problem is, we have been experiencing frequent (multiple times per day) crashes each day that require a restart of w3svc. What happens is that the cpu jumps to 99% and just sits there, and nothing works. They usually occur during the day, but we have had them at 4 am and on the weekends, so I think it is more than just the server being overloaded.

At least 90% of our pages run off ASP. Some of them use Access databases. Recently we just moved a bunch of our sites over to SQL server 7.0 (we are running sqlserver on the same machine) from Access. We had a lot of problems just after moving to SQL Server, until we started using stored procedures. At first the CPU would max out at 99 or 100%, with sql server and Inetinfo each taking up about 45%. Then after adding the stored procedures, the CPU now maxes out with Inetinfo.exe at 99%.

The ASP has been coded by a lot of different people, and may have some problems. I have done some brief checks for things like closing connections etc. I recently upgraded SQL server to the highest service pack. I have run virus scans and come up with nothing.

Any suggestions, ideas, shots in the dark or solid solutions are welcome,

Thanks!
 
From what you are describing it sounds like someone has got some screwy script on there. We had a guy write a small ASP program for our companies' website (a small game for customer to play) and it had a bug where it would go into in infinite loop and spawn other loops that would eventually bring the server down.

The other possibility is that the server is overloaded. What are the specs on it? Serving ASP pages and using a database will use up signifactly more power than serving static pages.
 
The server is a 450 mhz processor with 750 megs of RAM. Since it crashed at 4 am when the load was light, I am doubting that being overloaded is the sole problem.

Any ideas for catching a runaway script?
 
I think in IIS4 you can change the Application Protection to Isolated (High) and that should stop one script from bringing down the whole server. However you need to figure out who's site is doing it first.
 
You can make it so that a site runs in an isolated process. So, If I did this for one of the bigger sites, and if that site had the problem, only it would crash, correct? This would make finding the problem easier.
 
Yes that should work. This will cause IIS to use more memory though too. I'm not sure how much, it depends on how big the site is. Good Luck.

 
Back
Top