Hi all!!!!,
sometimes, we have some problems in our remedy AR Server and sometimes, the
Arsystem Server service but the armonitor service starts it again. The
problem is that our email engine service becomes like "zonbie", I mean, It
seems to be up, but the email engine doesnt send emails through Remedy.
We have found this document "The Email Engine is not running but startup
fails with error "AR System Email Engine is already running" in the BMC
Knowledge base, and it is:
Run ./emaild.sh stop to verify that the Email Engine is not running.
Restart the Email Engine.
With startup of the Email Engine, there is a new emaild.pid file created in
the install directory of the Email Engine. This new file will be populated
with the PID (Process ID) generated by the UNIX server for the process of
the Email Engine. The error "AR System Email Engine is already running" is
generated at startup of Email Engine when the entry in emaild.pid file is
a PID of a different process running on the UNIX.
Verify that this PID is not the process for the Email Engine. For example,
if the entry in emaild.pid file is 12345, the following command will check
for a running process with that PID:
ps -ef | grep 67890
If there is a running process for the Email Engine, the return from this
command will include information specific to the install directory of the
Email Engine. For example, the following is return from the above command
from a running Email Engine process
root 67890 12345 13 09:05:24 pts/4 0:03 /usr/j2re1.4.2_05/bin/java
-Djava.library.path=/usr/ar/AREmail/bmw63o9i -Dmail.
Please note that the information includes the install directory for this
Email Engine of /usr/ar/AREmail/bmw63o9i. This is the same directory where
the emaild.pid file exists with the entry of 67890.
If there is no running process for the Email Engine, the return will not
include this output and, at most, will have output just for that grep
command, similar to the following:
root 29845 29496 0 09:12:01 pts/4 0:00 grep 12345
With shutdown of Email Engine from ./emaild.sh stop command, the emaild.pid
file is deleted. Shutdown of Email Engine from shutdown of ARServer will
leave this emaild.pid file intact. Please refer to SW00244987 for software
bug documenting conditions where an existing emaild.pid file can impact
startup of Email Engine when the emaild.pid file contains a PID of a running
process.
When this document refers to "*SW00244987"*, what kind of document is
this?.... where could I find it?....
Thank you very much.!!!
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
