I guess you can switch on the API logging, and take a look what happens before the system will crash. If needed, you can then switch on filter and escalation logging if nessecary to see which part of the workflow is causing this.
I have had one occasion before where 1 corrupt entry in SHR:Company could take down the entire arserverd process. Found out about this one entry by examining the API and SQL logs. When I manually nulled the Diary field for this entry, the problem was resolved.
Never found out what the real issue was, but I never had any problems like this either.
Kind regards,
Michiel
On 10/6/06, Mathieu Pitre
<[EMAIL PROTECTED]> wrote:
Hi everyone,
ARS6.3
My development server is acting strangly with its arserverd process. In
fact, it takes all the CPU ressource and my other application which are
running on the same server crashes. My production server works perfectly. I
wonder where I should start investigating the source of the problem. I am
the only one using this development server and I do not query any heavy
transaction. Yesterday, we have shutdown the service and brough it back up
and it did the same thing(arserverd - CPU 98%) 5 to 10 minutes after. Is
there any system log file that would lead me to a specific path?
Mathieu Pitre
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
__20060125_______________________This posting was submitted with HTML in it___
