| Doc ID |
|
SOLN386704 |
| Version: |
|
1.0 |
| Status: |
|
Published |
| Published date: |
|
23 Jun 2026 |
Problem Clarification
Unable to start internal application server or appserver service on EPM
Cause
Following exception was seen when we check output of journalctl -xe on the CLI of EPM server.
-- Support: https://access.redhat.com/support
-- Unit appserver.service has begun starting up.
Jun 22 11:33:42 avaya.labs1.com bash[199408]: Existing PID file found during start.
Jun 22 11:33:42 avaya.labs1.com bash[199408]: Tomcat appears to still be running with PID 1135. Start aborted.
Jun 22 11:33:42 avaya.labs1.com bash[199408]: If the following process is not a Tomcat process, remove the PID file and try again:
Jun 22 11:33:42 avaya.labs1.com bash[199408]:
Jun 22 11:33:42 avaya.labs1.com bash[199408]: UID PID PPID C STIME TTY TIME CMD
Jun 22 11:33:42 avaya.labs1.com bash[199408]: root 1135 895 0 09:37 ? 00:00:00 /usr/libexec/sssd/sssd_be --domain implicit_files --uid 0 --gid 0 --logg...
Jun 22 11:33:42 avaya.labs1.com systemd[1]: appserver.service: Control process exited, code=exited status=1
Jun 22 11:33:42 avaya.labs1.com systemd[1]: appserver.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- The unit appserver.service has entered the 'failed' state with result 'exit-code'.
Jun 22 11:33:42 avaya.labs1.com systemd[1]: Failed to start Tomcat AppServer.
-- Subject: Unit appserver.service has failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- Unit appserver.service has failed.
-- The result is failed.
Solution
After removing the PID file of the appserver instance from the below path and starting the appserver service, the issue was resolved.
/opt/AppServer/Tomcat/tomcat/temp/mmsserver.pid
