Re: Stability complaints

This WebDNA talk-list message is from

2002

It keeps the original formatting. numero = 40414
interpreted = N
texte = >Dale,>>Thank you for sharing your detailed analysis. I'm pushing about 7-10 GB of>traffic a month right now and I get some crashes, but it's not been a daily>thing - however, any crash is not really acceptable.>>I have two questions:>>1. Where is the error log that you read the output from the crash?The output comes from restarting webcat after detecting that it's no longer responsive. When webcat dies on it's own, the output will be displayed on the terminal that originally started webcat (if it's still running). If a cron'd script started webcat, then often you will receive a delayed email with these messages.>2. Will you share the WebCatalog restart script? I know the command to>restart the server, but how do you run the script on crash?>>Running : OS 10.1.2, Webcat 4.0.something>>- Ben Swihart>Gotricities NetworkSure. I just put the latest version of my script up at:http://www.tfaw.com/downloads/webcatwatch.txtAnd I made a gzipped tarball with the entire package (includes a couple extra files referenced by the script) at:http://www.tfaw.com/downloads/webcat_up.tar.gzOnce installed, this script will detect 3 different types of webcat crash conditions and auto-restart the process. If root's email is properly configured, you will also receive email summaries of what happened, as well as appending to a logfile in /var/log/webcatwatch.log.Here's the header from webcatwatch.sh that summarizes what I'm detecting:# WHAT IT DOES:# Webcat 4.x on OSX can die in several ways:# 1) the process will exit# 2) the process is still running but stops responding (zombified)# 3) multiple webcat processes are started (i.e. a restart when the original process does not exit)# 4) webcat process runs away, sucking up increasing amounts of cpu and not responding to requests## We handle problem #1 by doing a ps to see if the Webcat process is running.# If it's not running, we restart it using WebCatalogCtl## Problem #2 is slightly harder to detect, because the webcat process is still# running, but all requests through http return sorry, webcatalog server not responding# to the browser. We use curl to detect this condition and use various amounts# of force to restart webcat, since a normal webcatalogctl restart doesn't always work.## Problem #3 happens when the WebCatalogCtl script restarts webcat but webcat does not exit cleanly.# Handled by using either kill -4 (in WebCatalogCtl4) or kill -9 to force the process to exit.# Problem 4 is only an issue only for some builds of 4.5 beta. The next beta release of webcat 4.5# will contain a threadlimit preference that essentially eliminates this problem.#I noticed Bob's script right before posting this. His method of testing for webcat running is probably more efficient, but I'm not sure if problem#2 would be detected by his script (I'll try it and see). With the latest build of webcat, I see problem #2 the most...Hope this helps.-Dale-------------------------------------------------------------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://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: Stability complaints (Bob Minor 2002)
Re: Stability complaints (Dale LaFountain 2002)
Re: Stability complaints (Bob Minor 2002)
Re: Stability complaints (Ben Swihart 2002)
Re: Stability complaints (Dale LaFountain 2002)

>Dale,>>Thank you for sharing your detailed analysis. I'm pushing about 7-10 GB of>traffic a month right now and I get some crashes, but it's not been a daily>thing - however, any crash is not really acceptable.>>I have two questions:>>1. Where is the error log that you read the output from the crash?The output comes from restarting webcat after detecting that it's no longer responsive. When webcat dies on it's own, the output will be displayed on the terminal that originally started webcat (if it's still running). If a cron'd script started webcat, then often you will receive a delayed email with these messages.>2. Will you share the WebCatalog restart script? I know the command to>restart the server, but how do you run the script on crash?>>Running : OS 10.1.2, Webcat 4.0.something>>- Ben Swihart>Gotricities NetworkSure. I just put the latest version of my script up at:http://www.tfaw.com/downloads/webcatwatch.txtAnd I made a gzipped tarball with the entire package (includes a couple extra files referenced by the script) at:http://www.tfaw.com/downloads/webcat_up.tar.gzOnce installed, this script will detect 3 different types of webcat crash conditions and auto-restart the process. If root's email is properly configured, you will also receive email summaries of what happened, as well as appending to a logfile in /var/log/webcatwatch.log.Here's the header from webcatwatch.sh that summarizes what I'm detecting:# WHAT IT DOES:# Webcat 4.x on OSX can die in several ways:# 1) the process will exit# 2) the process is still running but stops responding (zombified)# 3) multiple webcat processes are started (i.e. a restart when the original process does not exit)# 4) webcat process runs away, sucking up increasing amounts of cpu and not responding to requests## We handle problem #1 by doing a ps to see if the Webcat process is running.# If it's not running, we restart it using WebCatalogCtl## Problem #2 is slightly harder to detect, because the webcat process is still# running, but all requests through http return sorry, webcatalog server not responding# to the browser. We use curl to detect this condition and use various amounts# of force to restart webcat, since a normal webcatalogctl restart doesn't always work.## Problem #3 happens when the WebCatalogCtl script restarts webcat but webcat does not exit cleanly.# Handled by using either kill -4 (in WebCatalogCtl4) or kill -9 to force the process to exit.# Problem 4 is only an issue only for some builds of 4.5 beta. The next beta release of webcat 4.5# will contain a threadlimit preference that essentially eliminates this problem.#I noticed Bob's script right before posting this. His method of testing for webcat running is probably more efficient, but I'm not sure if problem#2 would be detected by his script (I'll try it and see). With the latest build of webcat, I see problem #2 the most...Hope this helps.-Dale-------------------------------------------------------------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://search.smithmicro.com/ Dale LaFountain

DOWNLOAD WEBDNA NOW!

Re: Stability complaints

2002

Top Articles:

Related Readings: