Re: [WebDNA] 6.2 Monitor
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108118
interpreted = N
texte = On Jan 18, 2012, at 10:00 AM, Donovan Brooke wrote: > Rob wrote: >> Hi All, >> >> Very rarely(once every couple months) I have WebDNA 6.2 stop, and drive the CPU nuts on Snow Leopard Server, and am looking at adding a script to keep an eye on it while I go on vacation. I found an old script... not sure where it come from or where I got it, but I had it on one of the old servers, and would like to get it working using launchd to start it, which isn't the problem. When I trigger the script, it comes up with "ps: No user named 'x'". Which is fairly obvious to those who no about these scripts, which I don't. >> >> So my question is, does anyone know how to get this working, or is there a better way? ... Script below. >> >> Rob > > > I wouldn't use that script for a couple reasons. > > First, It's not bad if your server shoots up to a 145% usage (2 CPU's) for short instances now and then.. > > Second, kill -9 is *not* a good way of stopping WebDNA... at least not for 6.2 which still uses WebDNAMonitor. > > Anyway, the script seems to contain logical problems in my opinion. > > If you were to use it, I'd change it to 199%... and change the 'kill -9' to '/Library/WebServer/WebCatalogEngine/WebCatalogCtl restart'. > > To fix the script, there is a change to how 'ps' functions in Snow Leopard.. > > basically change the instances of "ps -aux" in your script to "ps aux". > > To fix your CPU issue, I'd start looking into standard troubleshooting techniques.. looking at logs, looking for overgrown log files etc.. > > > Donovan > Thanks for the input Donovan. I'm not sure if I'm going to use it or not, at this point. Its just an avenue I'm looking at, unless there is a better solution. I did notice, however, that when WebDNA dies, the CPU hoovers around 60%, so I'm not sure this will even work when it acts up. I've been looking at the logs trying to pin out down, but it happens so rarely that its hard to get a handle on it... :-( .. I think all turn on everything in the Prefs Technical section for a while to see if I can catch it. Rob
Associated Messages, from the most recent to the oldest:
On Jan 18, 2012, at 10:00 AM, Donovan Brooke wrote: > Rob wrote: >> Hi All, >> >> Very rarely(once every couple months) I have WebDNA 6.2 stop, and drive the CPU nuts on Snow Leopard Server, and am looking at adding a script to keep an eye on it while I go on vacation. I found an old script... not sure where it come from or where I got it, but I had it on one of the old servers, and would like to get it working using launchd to start it, which isn't the problem. When I trigger the script, it comes up with "ps: No user named 'x'". Which is fairly obvious to those who no about these scripts, which I don't. >> >> So my question is, does anyone know how to get this working, or is there a better way? ... Script below. >> >> Rob > > > I wouldn't use that script for a couple reasons. > > First, It's not bad if your server shoots up to a 145% usage (2 CPU's) for short instances now and then.. > > Second, kill -9 is *not* a good way of stopping WebDNA... at least not for 6.2 which still uses WebDNAMonitor. > > Anyway, the script seems to contain logical problems in my opinion. > > If you were to use it, I'd change it to 199%... and change the 'kill -9' to '/Library/WebServer/WebCatalogEngine/WebCatalogCtl restart'. > > To fix the script, there is a change to how 'ps' functions in Snow Leopard.. > > basically change the instances of "ps -aux" in your script to "ps aux". > > To fix your CPU issue, I'd start looking into standard troubleshooting techniques.. looking at logs, looking for overgrown log files etc.. > > > Donovan > Thanks for the input Donovan. I'm not sure if I'm going to use it or not, at this point. Its just an avenue I'm looking at, unless there is a better solution. I did notice, however, that when WebDNA dies, the CPU hoovers around 60%, so I'm not sure this will even work when it acts up. I've been looking at the logs trying to pin out down, but it happens so rarely that its hard to get a handle on it... :-( .. I think all turn on everything in the Prefs Technical section for a while to see if I can catch it. Rob
Rob
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:
cybercash on OSX - was Executing remote AppleScript (2000)
totals (1997)
taxTotal, grandTotal (1997)
[WebDNA] Triggers.db wiped completely blank (2011)
[WebDNA] TCPConnect example doesn't work (2017)
URL for Discussion Archive (1997)
[WebDNA] preventing hackers from posting their own (altered) version of my form? (2009)
Multiple fields on 1 input (1997)
Multiple prices (1997)
form data submission gets truncated (1997)
(no subject) (1997)
WebCat2 - many [carts] on one template page? (1997)
PIXO support (1997)
PIXO (1997)
unclear on a simple [cart] ? (1998)
Overridding E-Mailer (1998)
Trigger Output (2003)
[SearchString] problem with [search] context (1997)
Support ?? (1997)
possible, WebCat2.0 and checkboxes-restated (1997)