Solutions to the failure and invalidity of opening nginx.pid

1. Problem Description

When we use nginx normally, we may often find that our pid is not found or lost, which will lead to an error as follows:

nginx: [error] open() "/var/run/nginx/nginx.pid" failed (2: No such file or directory)

Or:

nginx: [error] invalid PID number "" in "/var/run/nginx/nginx.pid"

2. Problem Analysis

• The nginx.pid file does not exist;
• The directory where nginx.pid is located does not exist.
  

3. Solution

Solution 1: Create a directory

For the problem:

Try to enter the /var/run/nginx directory:

The directory configured by nginx.pid here is set when compiling nginx, so the specific directory to be detected depends on what directory you set when compiling:
You can view it through: nginx -V command

If the directory is not found, create it:

mkdir /var/run/nginx

Where to create the directory here depends on what directory you configured during compilation, just like above.

Try to enter the newly created directory to check whether it is created successfully:

cd /var/run/nginx

Enter the nginx installation directory:

cd /usr/local/nginx

Get the installation directory of nginx: whereis nginx

Solution 2: Re-assign a configuration file

For the problem:

Enter sbin:

cd /sbin

Re-specify an nginx.conf file:

./nginx -c /usr/local/nginx/conf/nginx.conf

Reload the configuration file

./nginx -s reload

Solution 3: Modify the default pid

Enter the conf directory:

cd ../conf

Modify the nginx.conf file and execute the new nginx.pid:

#pid logs/nginx.pid;

This is the end of this article about solutions to the failure to open nginx.pid and its invalidation. For more information about the failure to open nginx.pid, please search for previous articles on 123WORDPRESS.COM or continue to browse the related articles below. I hope you will support 123WORDPRESS.COM in the future!