Re: webCat craps httpd
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 62504
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. thanks Jesse... according to the 'question mark': Causes the WebDNA - Commerce Edition engine to output debug information when WebDNA - Commerce Edition stops running due to a bus error. Information will be written into a file called "SignalCatcher.debug" in my case it doesn't crash. it just bogs down the server process that's taking care of the socket connection to the engine for a particular request making it unusable and taking up all the cpu power... anyway.. i turned it on... see if something gets written there.... thanks.. > 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/ > -- -- "In a world without walls or fences, who needs Windows and Gates?" ------------------------------------------------------------- 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. thanks Jesse... according to the 'question mark': Causes the WebDNA - Commerce Edition engine to output debug information when WebDNA - Commerce Edition stops running due to a bus error. Information will be written into a file called "SignalCatcher.debug" in my case it doesn't crash. it just bogs down the server process that's taking care of the socket connection to the engine for a particular request making it unusable and taking up all the cpu power... anyway.. i turned it on... see if something gets written there.... thanks.. > 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/ > -- -- "In a world without walls or fences, who needs Windows and Gates?" ------------------------------------------------------------- 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/
"kalin mintchev"
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:
Searching a field and returning the highest value (1997)
WC2b15 File Corruption (1997)
Setting up shop (1997)
AppleScript question (1997)
sorting dates (1999)
limitation found on group searching (1997)
Fwd: Problems with Webcatalog Plug-in (1997)
[LOOKUP] (1997)
pictures / referrer etc. (1998)
Associative lookup style? + bit more (1997)
Dark Horse Comics success story (1997)
[AppendFile] problem (WebCat2b13 Mac .acgi) (1997)
Webcat OSX (2001)
[taxRate] [TaxTotal] ? (1997)
WebCatalog 2.1 License for Sale (1998)
About that math question ... (2003)
[BoldWords] WebCat.acgib15Mac (1997)
spawn (1998)
[WebDNA] Require no empty field (2010)
Max Record length (1997)