Re: webCat craps httpd
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 62492
interpreted = N
texte = Yes I have. Turn on Catching Terminate Signal in the admin and start to look at the SignalCatcher.debug file. It will give you hints at which pages to start looking at. I sure wish WebDNA crashed more gracefully, but what can you expect? :) On Jul 7, 2005, at 12:09 AM, kalin mintchev wrote: > > i discovered today that the httpd hang-up on one of our machines is > WebCatalog's fault..... > > usually what happens is that one or more httpd processes - have seen > up to > around 25 - that use WebDNA are taking all the cpu processing power. > i have one running right now... > > eventually the number grows until i restart the server. non of the > other > active httpd processes are binded to a webcatalog socket. but all the > ones > that hang it are... i can not find the clients ip address in the logs > because it's not there - the offending page has not been "served" yet > in > order to write to the log. i suspect an infinite loop. but how to find > that one? there are 1000s of pages on this machine with webdna in them. > anybody gone trough this? > > and why is the socket connection still open after the client is gone? > -- Jesse Proudman Blue Box Group, LLC p. +1.800.613.4305 x801 e. jesse@blueboxgrp.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Yes I have. Turn on Catching Terminate Signal in the admin and start to look at the SignalCatcher.debug file. It will give you hints at which pages to start looking at. I sure wish WebDNA crashed more gracefully, but what can you expect? :) On Jul 7, 2005, at 12:09 AM, kalin mintchev wrote: > > i discovered today that the httpd hang-up on one of our machines is > WebCatalog's fault..... > > usually what happens is that one or more httpd processes - have seen > up to > around 25 - that use WebDNA are taking all the cpu processing power. > i have one running right now... > > eventually the number grows until i restart the server. non of the > other > active httpd processes are binded to a webcatalog socket. but all the > ones > that hang it are... i can not find the clients ip address in the logs > because it's not there - the offending page has not been "served" yet > in > order to write to the log. i suspect an infinite loop. but how to find > that one? there are 1000s of pages on this machine with webdna in them. > anybody gone trough this? > > and why is the socket connection still open after the client is gone? > -- Jesse Proudman Blue Box Group, LLC p. +1.800.613.4305 x801 e. jesse@blueboxgrp.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Jesse Proudman
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:
RAM crash (1998)
WebCat2b15MacPlugin - showing [math] (1997)
webcat license???? (1997)
RE: IIS4b2 and WebCatalog b19 (1997)
Separate SSL Server (1997)
Emailer (1997)
Change in Host? (1999)
[include ...] behavior (1997)
Counting downloads (1998)
2.0 Info (1997)
Replace Statement (1997)
Expected behavior? (1998)
Navigator 4.01 (1997)
Search Engine questions ... (2002)
Re[2]: Bugs still *not* fixed as promised ... (2000)
Discounts (1998)
OT: Typhoon (1998)
Big Databases (1997)
credit card (1997)
[BoldWords] WebCat.acgib15Mac (1997)