Startup Failed
Symptoms
During the deployment of the Spring Boot startup command in the action Start/Stop Spring Boot, the error message The SpringBoot 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 value of a parameter is improper or the parameter is incorrectly used.
- 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.
- Linux
lsof -i:8080 netstat -anp|grep 8080
- Windows
netstat -ano|findstr "8080"
- Linux
- 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
- Linux
![](https://support.huaweicloud.com/eu/deployman_faq/public_sys-resources/note_3.0-en-us.png)
- 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
- Ubuntu: ~/.bashrc and ~/.profile
- Centos: ~/.bashrc and ~/.bash_profile
- Set Java running parameters properly, and enter correct command line parameters in the corresponding text boxes. For details about the differences between system variables and command line parameters, see Start/Stop Spring Boot.
- Check whether the entered path is correct. If not, modify it and perform the deployment again.
- In the action Select Deployment Source, select a JAR file to download.
- If the problem persists, check the service startup logs and locate the fault based on the logs.
Starting or Stopping Spring Boot FAQs
- Invalid Spring Boot Path
- Startup Failed
- Environment Variables Are Not Configured
- Service Is Not Started Despite Successful Action Deployment
- Spring Boot Can Still Be Detected After Being Stopped (on Windows)
- Instruction
- 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