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:
- 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.
- Run the following command to check the Java environment. If JDK is not installed, install it through the action Install JDK.
![](https://support.huaweicloud.com/eu/deployman_faq/public_sys-resources/note_3.0-en-us.png)
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
- Install JDK that matches the Tomcat version.
- Check whether the entered path is correct. If not, modify it and perform the deployment again.
- 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
Starting or Stopping Tomcat FAQs
- Invalid Tomcat Path
- Stopping Failed
- Startup Failed
- Environment Variables Are Not Configured
- Service Is Not Started Despite Successful Action Deployment
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
more