George,
On the Unix's the script emaild.sh should get the job done to start or
stop the email engine. ( Email-Engine-710.pdf pg 41 has details)
A single run process should get the job done.
<email_engine_install_dir>/emaild.sh stop
&;<email_engine_install_dir>/emaild.sh start &;
You can likely find "< email_engine_install_dir >" with this:
grep emaild /etc/arsystem/< hostname >/armonitor.conf
As far as using an ARS application to do the stop/start... well...
here is what I would suggest..
1) Create a new form that you use data in the form to decide to run
the Escalation and to hang filters off of so that you can have much
more advanced logic for your Escalation processes.
2) Create a row in this new form that indicates that Escalations "X"
should run by using a character field that you put the name of the
escalation into and using a 'Status' = "Run" (or some other string
that you like).
3) Create the Escalation to check this new form with a run if like this:
'ESC Name' = "X" AND 'Status' = "Run"
Note: You may want to have a unique index on the 'ESC Name', or not,
depending on your total needs. You could also add a date time field so
that your Escalation could check every hour, and your date time field
could be updated by other processing to "skip" an hour for example.
4) Have the Escalation do a SET FIELD action to the one row(s) that
you find. This will trigger Filters on the new form in MODIFY.
5) Then write whatever logic you need in the filters.
For this case... maybe do a set field (from a filter) for "email
message in the queue ...with a status of SEND". If the 'Create-Date'
for the first record returned (assuming sort order on the form would
return the "oldest" record) is "old enough" then do a run process to
stop and start the email engine. If the date seems to indicated that
the Email engine is working within it' polling intervals... then do
nothing and let the modify finish.
You can even send notifications when the email engine is
"restarted" or "not -restarted", as desired too.
HTH.
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
On Fri, Jul 18, 2008 at 11:57 AM, 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"
