As a workaround, create your own startup and stop script and use that instead of the arsystem script to start and stop the AR System.
The only reason I can think of that the arsystem script may not be able to stop the email deamon is if the email deamon is started by some other user that the user the AR System is run by has no access to. So chances are you may be starting the AR System with one user and the email deamon with some other? This can technically be done of you comment the startup of the email from the armonitor file and decide to start the email engine seperately.. But in that case the parent process ID for the email will not be the arserverd process ID. Joe ________________________________ From: William Rentfrow <[email protected]> To: [email protected] Sent: Thu, October 15, 2009 12:25:51 PM Subject: Re: Email won't stop on server shutdown You're right - I botched the description below. The arsystem stop script + command runs and kills everything - except, of course, the email daemon. The "stop" section of the arsystem script appears to try to kill everything based off of the parent process ID. I'm not a script guru by any means but I can tell that the "stop" process is not calling emaild.sh stop. This is almost identical to 4 other servers we have running in the same configuration where I do not have this problem and I can't find any difference between them. William Rentfrow Principal Consultant, StrataCom Inc. [email protected] Corporate Website, www.stratacominc.com Blog, www.williamrentfrow.com 715-410-8156 C -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Grooms, Frederick W Sent: Thursday, October 15, 2009 11:12 AM To: [email protected] Subject: Re: Email won't stop on server shutdown emaild.sh stops arserverd (or did you mean arsystem script stops arserverd)? We are running Solaris 5.10 w ARS 7.1.0 patch 7 and I do not have that problem when doing an arsystem stop If the parent of the email engine java process is 1 then the server believes that the email engine is running as a detached (orphan) process. Check your armonitor.conf ( /etc/arsystem/{server}/armonitor.conf ) file to see how it is starting the engine. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of William Rentfrow Sent: Thursday, October 15, 2009 10:57 AM To: [email protected] Subject: Email won't stop on server shutdown ** This is Solaris - AR 7.1 patch 006 with the corresponding email engine. We also have IM 7.03, etc, installed which is irrelevant in this case. When I stop the server the email daemon won't stop. I always have to manually kill it and I'm unsure why - didn't find anything in the list archives either. The emaild.sh script appears to run and kill arserverd, the armonitor, and then any process with the same parent process id. However, when I do a ps -ef | grep <uid> I always see the parent process id for the email process as a slightly different number (+1) from the other parent process id. Is this a configuration issue? I have the same problem across three servers. It's not a show stopper by any means but it's a little annoying. William Rentfrow Principal Consultant, StrataCom Inc. [email protected] Corporate Website, www.stratacominc.com Blog, www.williamrentfrow.com 715-410-8156 C _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
