On this page

Show all

Help Center/ CodeArts Deploy/ FAQs/ Custom Application Actions/ Running Shell Commands/ Service Is Not Started But the Log Shows That Shell Commands Are Successfully Executed

Service Is Not Started But the Log Shows That Shell Commands Are Successfully Executed

Updated on 2023-11-28 GMT+08:00

View PDF

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 &

Parent topic: Running Shell Commands

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel