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 &
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.