**
Just a thought because I ran into something similar. Check to see if
you have server-side logging enabled. If you do, check on the sizes of
those log files.
I ran into a problem where the log files would get to be 2GB in size
(which is the max allowable by ARS). When I restarted the server, it
would "eat" RAM until it used it all up and then the process would
die. Thanks to armonitor, the cycle would repeat.
The solution for me was to remove the server side log files (or edit
the ar.conf/cfg file to disable logging) and then restart the server.
Hope this helps.
Derek
Adam Propeck wrote:
**
Hardware and platform details? I don't know if it makes a difference,
but I'm curious. I know I had read about some malloc issues on some
older Sun flavors.
On 4/26/06,
Munoz, Alvaro <[EMAIL PROTECTED]>
wrote:
Hi
fellas,
Im nos able to restart remedy service. Server went down for maintance
and after reboot Remedy service remains in "starting". In arerr.log I
get the error:
Wed Apr 26 18:14:54 2006 390600 : Malloc failed on server . (ARERR
300)
Wed Apr 26 18:14:54 2006 390600 : El servidor de AR System ha
terminado; se ha detectado un error grave. (ARNOTE 21).
Everything was running ok before the reboot.
When starting the service. ARServer.exe starts to get memory until
1,7GB!! When theres no RAM left it stops running ...
Why can be this process taking so much memory?
Thanks!
Alvaro
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
__20060125_______________________This posting was submitted with HTML
in it___
__20060125_______________________This posting was submitted with HTML in it___
|
