Thanks for the confirmation. Killing it is easy enough - that's what we've been doing.
I think I might have found another clue. At this point we have a total of 5 virtual Solaris machines running on one piece of hardware (more actually, but 5 Remedy servers). I just noticed that only a few of them can have the email engine running at a time as well. If I try to manually start the one I'm having problems with (which will start normally) it says the email engine is already running. The script is looking at the right install path and then pinging the RMIPort defined in EmailDaemon.properties. I suspect that since the RMIPort is the same for all servers (just confirmed that) we're having issues. What's the RMIPort? It's not in the documentation as far as I can tell. And does it have to be different if you have various email engines running on the same server? That would make sense....I know the Remedy servers themselves have to be on different ports (obviously...). 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 PRUITT, CHRISTOPHER Sent: Thursday, October 15, 2009 1:25 PM To: [email protected] Subject: Re: Email won't stop on server shutdown We have the same issue. This is how we have to manually stop the AREmail engine on Solaris. ► Open a Telnet Session to the server ► At the prompt enter the following command: ps -ef|grep AREmail ► Results look like this: ► Find the Process ID, for example above it would be 13089 ► At the prompt enter the following command along with the Process ID: kill 13089 and press Enter. This works for us. Not sure why we have to do this. However, we did find that stopping in AR System Administration: System>Email>Mailbox Configuration, does not always stop it. Christopher Pruitt Business Consulting III HP Enterprises Services [email protected] www.hp.com Confidentiality Notice: This message and any files transmitted with it are intended for the sole use of the entity or individual to whom it is addressed, and may contain information that is confidential, privileged, and exempt from disclosure under applicable law. If you are not the intended addressee for this e-mail, you are hereby notified that any copying, distribution, or dissemination of this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately destroy, erase, or discard this message. Please notify the sender immediately by return e-mail if you have received this e-mail by mistake. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of William Rentfrow Sent: Thursday, October 15, 2009 11:26 AM To: [email protected] 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" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
