Personally on a Unix/Linux server I leave the logs running all the time (just set a max size and the log will continuously wrap inside itself). Do a top or prstat -t and see what your load is on the server. Almost every Unix/Linux server I have worked with had more than enough horsepower to have the logs running all the time. When a process dies and is restarted the logs will be renamed to a .bak file and you can then look to see what the last actions were.
Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Dheeraj Kumar Sent: Wednesday, August 01, 2012 7:18 AM To: [email protected] Subject: Timeout in Remedy - ARS 7.1 ** Hi List, Looking for suggestions on how to get to the root of Timeout issues. Of late we have been observing regular ARS hangs. arerror log only says Dispatch,BRIE,Assignment engine timeouts(ARERR 93). Further the ARMonitor log has the below entry each time the issue occurs. Wed Aug 1 04:33:37 2012 (ARNOTE 0) Wed Aug 1 04:33:37 2012 ARMonitor child process (pid:23119) died with 65280. ./apsvcae.sh Does above entry in ARMonitor log suggest something wrong with assignment engine? When we manually restart the arservice, it works well and after a month or so the issue occurs again. Any suggestions on how we can debug? We don't have any server side logging enabled as issue occurs randomly- once in a month or 45 days. Server details : Server group of 3 servers(Solaris os), ARS 7.1 Patch 9 and ITSM 6.3. Regards, Dheeraj _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
