Re: [WebDNA] 6.2 Monitor

This WebDNA talk-list message is from

2012


It keeps the original formatting.
numero = 108121
interpreted = N
texte = Maybe the thought he was funny.=20 Was your old server intel based?=20 did you turn on the troubleshooting tools? On Jan 18, 2012, at 6:37 PM, Rob wrote: > Uuuuh...the server is only six months old.... how new do you want me = to try?... All that's happened is we retired an old server, that wasn't = having any problems, but it was over 5 years old, and we just didn't = trust it any more, and to replace internal hardware would cost more then = purchasing a new one. >=20 >=20 > Rob >=20 >=20 > On Jan 18, 2012, at 4:35 PM, William DeVaul wrote: >=20 >> Try a new server. Worked wonders for me. >>=20 >> Bill >>=20 >> On Wed, Jan 18, 2012 at 11:18 AM, Rob wrote: >>=20 >>>=20 >>> On Jan 18, 2012, at 10:00 AM, Donovan Brooke wrote: >>>=20 >>>> Rob wrote: >>>>> Hi All, >>>>>=20 >>>>> 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. >>>>>=20 >>>>> So my question is, does anyone know how to get this working, or is >>> there a better way? ... Script below. >>>>>=20 >>>>> Rob >>>>=20 >>>>=20 >>>> I wouldn't use that script for a couple reasons. >>>>=20 >>>> First, It's not bad if your server shoots up to a 145% usage (2 = CPU's) >>> for short instances now and then.. >>>>=20 >>>> Second, kill -9 is *not* a good way of stopping WebDNA... at least = not >>> for 6.2 which still uses WebDNAMonitor. >>>>=20 >>>> Anyway, the script seems to contain logical problems in my opinion. >>>>=20 >>>> If you were to use it, I'd change it to 199%... and change the = 'kill -9' >>> to '/Library/WebServer/WebCatalogEngine/WebCatalogCtl restart'. >>>>=20 >>>> To fix the script, there is a change to how 'ps' functions in Snow >>> Leopard.. >>>>=20 >>>> basically change the instances of "ps -aux" in your script to "ps = aux". >>>>=20 >>>> To fix your CPU issue, I'd start looking into standard = troubleshooting >>> techniques.. looking at logs, looking for overgrown log files etc.. >>>>=20 >>>>=20 >>>> Donovan >>>>=20 >>>=20 >>> Thanks for the input Donovan. >>>=20 >>> 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. >>>=20 >>> 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. >>>=20 >>> Rob >>>=20 >>>=20 >>>=20 >>>=20 >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>>=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.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)
Maybe the thought he was funny.=20 Was your old server intel based?=20 did you turn on the troubleshooting tools? On Jan 18, 2012, at 6:37 PM, Rob wrote: > Uuuuh...the server is only six months old.... how new do you want me = to try?... All that's happened is we retired an old server, that wasn't = having any problems, but it was over 5 years old, and we just didn't = trust it any more, and to replace internal hardware would cost more then = purchasing a new one. >=20 >=20 > Rob >=20 >=20 > On Jan 18, 2012, at 4:35 PM, William DeVaul wrote: >=20 >> Try a new server. Worked wonders for me. >>=20 >> Bill >>=20 >> On Wed, Jan 18, 2012 at 11:18 AM, Rob wrote: >>=20 >>>=20 >>> On Jan 18, 2012, at 10:00 AM, Donovan Brooke wrote: >>>=20 >>>> Rob wrote: >>>>> Hi All, >>>>>=20 >>>>> 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. >>>>>=20 >>>>> So my question is, does anyone know how to get this working, or is >>> there a better way? ... Script below. >>>>>=20 >>>>> Rob >>>>=20 >>>>=20 >>>> I wouldn't use that script for a couple reasons. >>>>=20 >>>> First, It's not bad if your server shoots up to a 145% usage (2 = CPU's) >>> for short instances now and then.. >>>>=20 >>>> Second, kill -9 is *not* a good way of stopping WebDNA... at least = not >>> for 6.2 which still uses WebDNAMonitor. >>>>=20 >>>> Anyway, the script seems to contain logical problems in my opinion. >>>>=20 >>>> If you were to use it, I'd change it to 199%... and change the = 'kill -9' >>> to '/Library/WebServer/WebCatalogEngine/WebCatalogCtl restart'. >>>>=20 >>>> To fix the script, there is a change to how 'ps' functions in Snow >>> Leopard.. >>>>=20 >>>> basically change the instances of "ps -aux" in your script to "ps = aux". >>>>=20 >>>> To fix your CPU issue, I'd start looking into standard = troubleshooting >>> techniques.. looking at logs, looking for overgrown log files etc.. >>>>=20 >>>>=20 >>>> Donovan >>>>=20 >>>=20 >>> Thanks for the input Donovan. >>>=20 >>> 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. >>>=20 >>> 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. >>>=20 >>> Rob >>>=20 >>>=20 >>>=20 >>>=20 >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>>=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us Robert Minor

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:

Million product store (2003) Shipping based in distance and weight (1999) LinkExchange (1997) REPOST: Large founditems loops (2000) two unique banners on one page (1997) [shownext] not displaying anything but first indices found (2000) Webcat no longer supported? (2006) Re:quit command on NT (1997) Searchable WebCat (etc.) Docs ? (1997) Check Boxes (2000) Problems appending to database (1997) when is date system date or order date? (1997) Wanted: Broader string manipulation functions (1997) Stinkin' [Referrer] (1998) WebCatalog and barcodes (2000) WebCat 5 Intranet Question (2003) (2000) JavaScript Image Problem (1998) Uploading very large image files (2003) I'm new be kind (1997)