Help Center/ CodeArts Deploy/ FAQs/ Custom Application Actions/ Starting or Stopping Tomcat/ Startup Failed
Updated on 2023-05-26 GMT+08:00
View PDF
Share

Startup Failed

Symptoms

During the deployment of the Tomcat startup command in the action Start/Stop Tomcat, the error message The Tomcat service startup failed is displayed.

Cause Analysis

The possible causes are as follows:

  • The port is occupied.
  • JDK is not installed or environment variables are incorrectly configured.
  • The JDK version does not match the Tomcat version.
  • The entered absolute path is incorrect.

Solution

Perform the following steps to rectify the fault:

  1. Run the following command to check whether the port is occupied. If the port is occupied, change the port number and perform the deployment again.
    • Linux

      lsof -i:8080

      netstat -anp|grep 8080

    • Windows

      netstat -ano|findstr "8080"

  1. Run the following command to check the Java environment. If JDK is not installed, install it through the action Install JDK.
    • Linux

      java -version

      which java

    • Windows

      java -version

Scenario 1: If the Linux OS is in use and JDK is manually installed, add the JDK environment variables to the following files because the current startup operation is no_login:

  • Ubuntu: ~/.bashrc and ~/.profile
  • Centos: ~/.bashrc and ~/.bash_profile

    The following is a configuration example of the environment variables:

    • export JAVA_HOME=/usr/local/jdk/jdk1.8.0_151
    • export CLASS_PATH=$JAVA_HOME/lib:$JAVA_HOME/jre/lib
    • export PATH=$JAVA_HOME/bin:$PATH

Scenario 2: If the Linux OS is in use and JDK of the version openjdk-1.8.0 is installed using the action Install JDK, you do not need to manually configure JDK. However, you must delete the JDK environment variables from the following files:

  • Ubuntu: ~/.bashrc and ~/.profile
  • Centos: ~/.bashrc and ~/.bash_profile
  1. Install JDK that matches the Tomcat version.
  2. Check whether the entered path is correct. If not, modify it and perform the deployment again.
  3. If the problem persists, check the Tomcat startup logs and locate the fault based on the logs. The logs are saved in the following directories:
    • ${HOME}/tomcat/logs/catalina.out
    • ${HOME}/tomcat/logs/catalina.log