Startup Failed
Symptoms
When the startup command in Start/Stop Go Service is deployed, the log shows "The Go service has been started. If you need to restart, please stop the service first! ", which means that the startup fails".
Analysis
The service has been started. When the startup command is executed again, an error is reported.
Solution
Stop the service by executing Stop Go Service, and then run the startup command again.
Or log in to the server to stop the started services, and then run the startup command again.
Starting/Stopping Go Service FAQs
- The Go Service Path Is Incorrect
- Startup Failed
- Environment Variables Are Not Configured
- Deployment Is Successful, But the Service Is Not Started
- 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