Last post Nov 30, 2005 06:58 AM by Codepic
Nov 21, 2005 12:37 PM|niordanov|LINK
Nov 21, 2005 01:03 PM|sowens|LINK
Nov 21, 2005 01:31 PM|niordanov|LINK
It's Win2K SP4, MSDE 2000 running on the same box.
Nov 21, 2005 06:31 PM|cathal|LINK
MSDE has a similar issue, except it can support some more connections before the
governor kicks in . Normally the requests are queued, so it shouldn't be the issue, only the wait time has grown very large (you can run sp_who to check users/processes)
Nov 22, 2005 08:01 AM|niordanov|LINK
Nov 22, 2005 12:48 PM|sowens|LINK
Nov 22, 2005 12:54 PM|niordanov|LINK
Nov 28, 2005 03:16 AM|niordanov|LINK
We got the error again. Here's the memory usage info:
aspnet_wp.exe - 434MB
sqlservr.exe - 257MB
CPU usage - 68%
MEM usage - 905MB
I guess we need more RAM... :(
Nov 28, 2005 04:59 AM|Codepic|LINK
Nov 28, 2005 07:20 AM|niordanov|LINK
Nov 28, 2005 07:35 AM|sowens|LINK
How long were you up this time before the crash? 10-20k page hits is a good size, but the machine should be able to take it. The one thing I don't recommend doing is have SQL running on the same box as IIS for security and performance reasons. You can tune
DNN, but I am not sure that is the whole picture on your server and it's issues.
I would watch your CPU and your Memory closely and see if the two in combination are bringing down the server. aspnet_wp.exe should take up to 60% or so of your memory. I would also watch the number of users online at the same time and how it affects your CPU
When you throw sqlservr.exe and the OS on top of that you can see that you are running out of memory fast. Your looking at 70% of memory being used without including the OS. That is not a lot of resources left and I would say the server needs scaled up or out.
Another Gig is probably cheap, depending on your budget. But I wouldn't buy it till I was sure the CPU isn't helping the crashes along as well.
Nov 28, 2005 07:51 AM|lomaxx|LINK
The one thing I don't recommend doing is have SQL running on the same box as IIS for security and performance reasons. You can tune DNN, but I am not sure that is the whole picture on your server and it's issues.
Nov 28, 2005 10:23 AM|niordanov|LINK
Nov 28, 2005 11:57 AM|sowens|LINK
Nov 28, 2005 12:00 PM|Codepic|LINK
The files in /Portals/_Default/Logs are about 100K-800K each. This must be because we're storing the site log and statistics in MSDE. Shall I try to delete the logs and stats from MSDE instead?
Nov 28, 2005 12:07 PM|niordanov|LINK
Nov 28, 2005 08:40 PM|cathal|LINK
Is DotNetNuke the only site you have running? Do you have any custom code, com objects, etc above the normal install? Leaks are possible, but if it is within the .Net framework, I believe leaks are taken care of by shutting down the old object and creating
a new one for you. I have seen leaking COM objects crash servers, as I am sure most of you have.
Nov 28, 2005 10:35 PM|sowens|LINK
Nov 29, 2005 08:47 AM|niordanov|LINK
Is DotNetNuke the only site you have running? Do you have any custom code, com objects, etc above the normal install?
Nov 29, 2005 09:58 AM|niordanov|LINK
Nov 29, 2005 11:26 AM|Codepic|LINK
Nov 30, 2005 03:33 AM|niordanov|LINK
Nov 30, 2005 06:58 AM|Codepic|LINK