How to troubleshoot if Tomcat service cannot be started.


2016-11-16 12:54:03 UTC


2017-04-24 12:08:14 UTC


Was this article helpful?

Have more questions?

Submit a request

How to troubleshoot if Tomcat service cannot be started.

Applicable to:

  • Plesk 12.5 for Linux
  • Plesk 11.5 for Linux
  • Plesk 12.0 for Windows
  • Plesk 12.0 for Linux


After starting Tomcat through Plesk or command line its status is showing as 'Off' and java processes are not displayed on the server via SSH.


Perform the following steps in order to diagnose and fix the problem.

  1. Look into /var/log/tomcat*/catalina.out for any startup errors.

If there is the following error:

        Memory database file psa-users/DOMAIN.COM.xml cannot be read.

apply the KB article article.

  1. Try start Tomcat from the command line *
    $PRODUCT_RC_D/tomcat4 start

2.1. If you see the following messages:

         Starting tomcat4: process already running
  • and there are the following messages in the /usr/local/psa/admin/logs/panel.log :
        [2015-06-19 21:40:36] DEBUG [util_exec] [55843efceba3c] Starting: tomcatmng /usr/local/psa/admin/bin/tomcatmng '--status'
    [2015-06-19 21:40:36] DEBUG [util_exec] [55843efceba3c] Finished in 0.02103s, Result: TRUE

It means that only Plesk shows the service as stopped. This is a Plesk internal issue with ID #PPPM-2969 , which will be fixed in future Plesk updates.

  • If there are no java processes running and the following command
        # ps ax | grep java | grep -v grep

returns nothing. Then remove the following files

        #rm -f /var/run/tomcat*.pid /var/lock/subsys/tomcat*

and try to start Tomcat again:

    #$PRODUCT_RC_D/tomcat4 start

2.2. If Tomcat fails to start with some class "No such file or directory" exception, check that there are no broken symlinks in /usr/share/tomcat*/common/lib/ directory.

2.3. If Tomcat fails to start with the messages like below:

        /usr/bin/rebuild-jar-repository: error: could not find jta Java extension for this JVM
/usr/bin/rebuild-jar-repository: error: All detected jars were not found for this jvm

check the following:

  • several different Tomcat packages installed;

  • some file missing or problem with permission/ownerships.

  • If it is impossible to find the reason, try to remove all Java and Tomcat packages and reinstall them anew. Find installed packages with the command like:

    #rpm -qa | egrep '(java)|(tomcat)|(j2sdk)'

\* Refer to the KB article .

Have more questions? Submit a request
Please sign in to leave a comment.