Re: How to stop Arreror.log

[Heider, Stephen]

** Kathy,   The escalation engine may be stopped but the workflow might still be running.  For example, if an escalation modified 1000 tickets and workflow updates or creates 1000 more tickets then it may take a while before processing is complete... Just speculation here because I don't know how long the escalations engine was disabled. If it's been a while then there is likely another cause.    To see if the escalation engine is actually still running turn on Escalation Logging.  If it is running then you will see new entries.   As far as I am aware there is no way to turn off error logging (arerror.log); this is built in to ARS.  However, there are ways to keep it from filling up your hard drive.  One method is to delete the arerror.log file every 1 minute.  Since the escalation engine is disabled create a Windows Scheduled Task (or a Cron job with *nix).  ARS does not keep this file open in between errors so you should be able to delete it.   If you want to keep the error log file you could create a batch file or script that moves (instead of deletes) the arerror.log file to another folder, then zips it... Or, simply move it to another drive and rename it.  And then schedule it to run every 1 minute.   HTH   Stephen   From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kathy Morris Sent: Wednesday, May 03, 2006 2:03 PM To: arslist@ARSLIST.ORG Subject: How to stop Arreror.log ** I created an escalation -- which is not working.  I disabled the escalation, however in the arerror.log this is still running.  Why is the escalation still running, even though it is disabled?  The errors are filling up our disk space fast.  Is there a way to stop this from writing to the arreror.log?     __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___