Help Center>
CodeArts Deploy>
FAQs>
Custom Application Actions>
Start/Stop Go Service>
Deployment Is Successful, But the Service Is Not Started
Updated on 2024-07-04 GMT+08:00
Deployment Is Successful, But the Service Is Not Started
Symptoms
The command for starting Go is successfully deployed during the deployment of the action Start/Stop Go Service, but the service is not started.
Analysis
- The waiting time is too short. As a result, the service is not started when the waiting time ends.
- If the service still fails to be started after the waiting time is adjusted to a longer time, check whether any other causes exist.
Solution
- Adjust the waiting time.
- Log in to the server where the service is deployed to manually start the service or view logs to locate the service fault.
Parent topic: Start/Stop Go Service
Start/Stop 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.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
