Re: [WebDNA] 6.2 Monitor

This WebDNA talk-list message is from

2012


It keeps the original formatting.
numero = 108117
interpreted = N
texte = 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 -- Donovan Brooke Euca Design Center www.euca.us Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] 6.2 Monitor (Kenneth Grome 2012)
  2. Re: [WebDNA] 6.2 Monitor (christophe.billiottet@webdna.us 2012)
  3. Re: [WebDNA] 6.2 Monitor (William DeVaul 2012)
  4. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  5. Re: [WebDNA] 6.2 Monitor (christophe.billiottet@webdna.us 2012)
  6. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  7. Re: [WebDNA] 6.2 Monitor (christophe.billiottet@webdna.us 2012)
  8. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  9. Re: [WebDNA] 6.2 Monitor (christophe.billiottet@webdna.us 2012)
  10. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  11. Re: [WebDNA] 6.2 Monitor (Donovan Brooke 2012)
  12. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  13. Re: [WebDNA] 6.2 Monitor (Donovan Brooke 2012)
  14. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  15. Re: [WebDNA] 6.2 Monitor (Donovan Brooke 2012)
  16. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  17. Re: [WebDNA] 6.2 Monitor (christophe.billiottet@webdna.us 2012)
  18. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  19. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  20. Re: [WebDNA] 6.2 Monitor (Donovan Brooke 2012)
  21. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  22. Re: [WebDNA] 6.2 Monitor (Kenneth Grome 2012)
  23. Re: [WebDNA] 6.2 Monitor (Donovan Brooke 2012)
  24. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  25. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  26. Re: [WebDNA] 6.2 Monitor (Robert Minor 2012)
  27. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  28. Re: [WebDNA] 6.2 Monitor (William DeVaul 2012)
  29. Re: [WebDNA] 6.2 Monitor (Rob 2012)
  30. Re: [WebDNA] 6.2 Monitor (Donovan Brooke 2012)
  31. [WebDNA] 6.2 Monitor (Rob 2012)
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 -- Donovan Brooke Euca Design Center www.euca.us Donovan Brooke

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:

Frames and WebCat (1997) WebDNA-Talk Digest mode broken (1997) Text data with spaces in them... (1997) WebCat2b13MacPlugIn - syntax to convert date (1997) F2 to F3 rocky transition (1997) [WebDNA] FastCGI version confusion (2011) Windows 2.1b2 Append Bug? (1997) [OT] Server check please (2006) 2.1b3 --> way slow (1997) SiteGuard Admin Feature ? (1997) serial number dishing (1997) There's a bug in the math context ... (1997) WebCat2b13MacPlugin - [math][date][/math] problem (1997) too many nested tags ... (1997) [SearchString] problem with [search] context (1997) WCS Newbie question (1997) Incrementing a number (1998) emailer prob (1998) Changing RAM-cached browser values ... (2000) off-topic - printinglib 68K (1997)