Thanks for the input Donovan.
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 scrip=t 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 CP=U'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 =9;kill -9' to '/Library/WebServer/WebCatalogEngine/WebCatalogCtl re=start'.
>
> 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 t=o "ps aux".
>
> To fix your CPU issue, I'd start looking into standard troubleshoo=ting techniques.. looking at logs, looking for overgrown log files etc..
>
>
> 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 not=ice, 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... :-( =A0.. I think all turn o=n everything in the Prefs Technical section for a while to see if I can cat=ch it.
Rob
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g=t;.
To unsubscribe, E-mail to: <talk=-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
Thanks for the input Donovan.
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 scrip=t 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 CP=U'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 =9;kill -9' to '/Library/WebServer/WebCatalogEngine/WebCatalogCtl re=start'.
>
> 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 t=o "ps aux".
>
> To fix your CPU issue, I'd start looking into standard troubleshoo=ting techniques.. looking at logs, looking for overgrown log files etc..
>
>
> 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 not=ice, 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... :-( =A0.. I think all turn o=n everything in the Prefs Technical section for a while to see if I can cat=ch it.
Rob
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g=t;.
To unsubscribe, E-mail to: <talk=-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
DOWNLOAD WEBDNA NOW!
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...