And the process says "ouch" and disappears never to be seen again.

Axton

On Mon, Jul 21, 2008 at 4:15 PM, Gary Opela (Corporate)
<[EMAIL PROTECTED]> wrote:
> Kill -9 !!!!!!!
>
> Thanks,
>
>
>
> Gary Opela, Jr., RSP
>
> Remedy Engineer
>
> Leader Communications, Inc.
>
> http://www.5pointleader.com
>
> http://www.lcibest.com
>
> Best Product, Best People, Best PriceTM
>
> An ISO 9001:2000 Certified, CMMI(r) Level 3 Rated Company
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList) [mailto:[EMAIL 
> PROTECTED] On Behalf Of Ramey, Anne
> Sent: Monday, July 21, 2008 1:16 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: Help with a UNIX script to STOP the AREmail daemon
>
> Depending how badly it is hung and why, that may work and may not.  I've 
> actually had to kill the java process before.  That tends to be how we do it 
> at this point.
>
> Anne Ramey
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList) [mailto:[EMAIL 
> PROTECTED] On Behalf Of Jason Miller
> Sent: Sunday, July 20, 2008 12:33 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: Help with a UNIX script to STOP the AREmail daemon
>
> Hi George,
>
> Interestingly enough we see the same thing with the window email
> engine. It has bee a few years but you should be able to call
> emaild.sh script (I think that is the name) and give it a stop
> parameter. Once armonitor sees that it is stopped it should
> automatically start up again.
>
> Jason
>
>
>
> On 7/18/08, Payne, George <[EMAIL PROTECTED]> wrote:
>> Hey gang...
>>
>>
>>
>> Occasionally the ARSystem Email Engine will just stop working.  The
>> DAEMON is running and so the ARMONITOR does not realize that the service
>> needs to be re-started because the PROCESS is still running.
>>
>>
>>
>> What I would like to do is have an ESCALATION run a PROCESS on the
>> server to KILL the AREmail process so that ARMONITOR would automatically
>> restart it.
>>
>>
>>
>> One caution:
>>  I don't want to run it against EVERY unsent email message in the
>> queue...it just needs to run against the OLDEST with a status of SEND.
>>
>>
>>
>> Has anyone written such an escalation and the associated SCRIPT that
>> would have to be written to the UNIX side of the process call?
>>
>>
>>
>> You help, as always, would be greatly appreciated!
>>
>>
>> Thanks,
>> Gp
>>
>>
>>
>> George Payne
>>
>> Corporate Applications Developer
>>
>> Electric Reliability Council of Texas
>>
>> (512) 248-3940
>>
>> [EMAIL PROTECTED]
>>
>>
>> _______________________________________________________________________________
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to