Help Center/ CodeArts Deploy/ FAQs/ Custom Application Actions/ Starting or Stopping Nginx/ Deploying the Command for Stopping Nginx When Nginx Is Not Started

Updated on 2023-05-26 GMT+08:00

View PDF

Deploying the Command for Stopping Nginx When Nginx Is Not Started

Symptoms

An error message containing nginx.pid is displayed.

"nginx: [error] open() \"/home/xxx/nginx/logs/nginx.pid\" failed (2: No such file or directory)"

Cause Analysis

After Nginx is started, the process ID is saved in nginx.pid. Nginx can be stopped based on the process ID. If the Nginx process does not exist, an error message indicating that the nginx.pid file cannot be found will be displayed when you deploy the stop and quit commands.

Solution

Do not deploy the command for stopping Nginx if it is not started.

Parent topic: Starting or Stopping Nginx

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.See the reply and handling status in My Cloud VOC.

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

For any further questions, feel free to contact us through the chatbot.