Re: [WebDNA] WebDNA 4.5.1 process DBServer.exe memory
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 100418
interpreted = N
texte = At 01:09 PM 7/29/2008, you wrote:>Greg Kesler wrote:>>Does anyone have any idea how to narrow the "bad code" down to a >>specific web site. There are several web sites running on the box.>>Thank you in adavance!>>-Greg.>>>Hi Greg,>>Personally, I am not as familiar about process tracing on a windows>box as I am with *nix boxes. Maybe someone else here can point you>to utilities that can trace/watch these processes. W2003 may even>have some.??>>Other than Windows specific (tracing) solutions, Some places you >might start are:>- Temporarily turning on LogErrorMessages (if 4.5.x had that feature??)> If it does, only turn this on until the machine crashes.. turn it off> after you reboot as it's not good to run with this feature always on.I have the LogErrorMessages enabled from the webDNA preferences.There have been no entries in the ErrorLog.txt file since the LogErrorMessages was enabled over two hours ago.>- The most active domains are usually the most likely to be the problem.>>- If you isolate the problem to a particular Domain... you can comment out> sections of code [!]... [/!] to test if that fixes things.>>- Some notorious causes of clogged processes are:> * Missing Carriage returns at the end of a database file (munged databases> in general)Checking the DB files> * Large Searches gone rogueI am new to using webDNA ( I inherited it from the previous web person. )> * Other loops and CPU intensive thingsCPU process does not appear to be an issue as the CPU load stays relatively low. Just the memory allocation to the DBServer.exe process seems to have gone runaway.>- Lastly, note that "bad code" may be somewhat transparent until the server> actually gets some "hits".. then the "bad code" is heightened and can> cause these 100% CPU and clogged process problems.This sounds promising as the issue presents itself at random times.If anyone else has any suggestions, I would welcome any assistance on this I can have.Thank you,Greg>Upgrading may not help "Bad Code" but it may help if the problem is related>to a mis-match in Hardware/Software compatibility. I don't know off-hand>(without digging) what the hardware requirements were for 4.5.x. are. We will>be releasing info on how to upgrade soon.>>Donovan>>>>>>>-->Donovan D. Brooke PH/FAX: 1 (608) 291-2024>------------------------------------------------>VP>WebDNA Software Corporation>16192 Coastal Highway>Lewes, DE 19958>--------------------------------------------------------->This message is sent to you because you are subscribed to>the mailing list
.>To unsubscribe, E-mail to:
Associated Messages, from the most recent to the oldest:
At 01:09 PM 7/29/2008, you wrote:>Greg Kesler wrote:>>Does anyone have any idea how to narrow the "bad code" down to a >>specific web site. There are several web sites running on the box.>>Thank you in adavance!>>-Greg.>>>Hi Greg,>>Personally, I am not as familiar about process tracing on a windows>box as I am with *nix boxes. Maybe someone else here can point you>to utilities that can trace/watch these processes. W2003 may even>have some.??>>Other than Windows specific (tracing) solutions, Some places you >might start are:>- Temporarily turning on LogErrorMessages (if 4.5.x had that feature??)> If it does, only turn this on until the machine crashes.. turn it off> after you reboot as it's not good to run with this feature always on.I have the LogErrorMessages enabled from the webDNA preferences.There have been no entries in the ErrorLog.txt file since the LogErrorMessages was enabled over two hours ago.>- The most active domains are usually the most likely to be the problem.>>- If you isolate the problem to a particular Domain... you can comment out> sections of code [!]... [/!] to test if that fixes things.>>- Some notorious causes of clogged processes are:> * Missing Carriage returns at the end of a database file (munged databases> in general)Checking the DB files> * Large Searches gone rogueI am new to using webDNA ( I inherited it from the previous web person. )> * Other loops and CPU intensive thingsCPU process does not appear to be an issue as the CPU load stays relatively low. Just the memory allocation to the DBServer.exe process seems to have gone runaway.>- Lastly, note that "bad code" may be somewhat transparent until the server> actually gets some "hits".. then the "bad code" is heightened and can> cause these 100% CPU and clogged process problems.This sounds promising as the issue presents itself at random times.If anyone else has any suggestions, I would welcome any assistance on this I can have.Thank you,Greg>Upgrading may not help "Bad Code" but it may help if the problem is related>to a mis-match in Hardware/Software compatibility. I don't know off-hand>(without digging) what the hardware requirements were for 4.5.x. are. We will>be releasing info on how to upgrade soon.>>Donovan>>>>>>>-->Donovan D. Brooke PH/FAX: 1 (608) 291-2024>------------------------------------------------>VP>WebDNA Software Corporation>16192 Coastal Highway>Lewes, DE 19958>--------------------------------------------------------->This message is sent to you because you are subscribed to>the mailing list .>To unsubscribe, E-mail to:
Greg Kesler
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[searh] or [shownext]problem (1998)
New Lawsuit Alleges Unitedhealth/Pacificare Deceived (2006)
WebCat2b15MacPlugin - showing [math] (1997)
Country & Ship-to address & other fields ? (1997)
[convertchars] Problem (2000)
[Feature Request] Stronghold security variables that cannot be (2000)
Setting up shop (1997)
SSL, WebSTAR, WebCatalog (1998)
Cart date/time (2006)
[WebDNA] Fails from http:// but works from file:/// (2009)
Merry Christmas (1999)
[sendmail] (2000)
Not really WebCat (1997)
One Hour Email (2002)
WebCat2 Append problem (B14Macacgi) (1997)
PCS Frames (1997)
Loop code problem (2000)
Searching multiple Databases (1997)
File Upload (1997)
unable to launch acgi in WebCat (1997)