Service Is Not Started But the Log Shows That Shell Commands Are Successfully Executed
Symptoms
The log shows that the deployment of the shell command /usr/local/tomcat/bin/startup.sh is successful, but no process corresponding to the service is found on the server.
Cause Analysis
When Ansible deploys a shell command, the corresponding process is forcibly stopped after the deployment is complete. As a result, the service process cannot be found.
Solution
Make the shell command run in the background.
nohup /usr/local/tomcat/bin/startup.sh &
Running Shell Commands FAQs
- A Message Indicating an Operation Failure Is Displayed During Action Run Shell Commands Deployment
- Service Is Not Started But the Log Shows That Shell Commands Are Successfully Executed
- Unidentified Shell Commands Are Used
- Shell Command References a File or Folder That Does Not Exist
- How Does a Shell Command Reference Parameters?
- Deployment of the Action Run Shell Commands Times Out
- Interactive Shell Commands Are Used
- Shell Command Deployment Times Out After the su Command Is Executed to Switch the User
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- 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
- Other FAQs
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
more