Where is nginx pid file

And sudo service nginx restart gives this error. I think nginx fails to start because old one still alive. I will recommend stopping nginx by killing it's master process first. The nginx is not shutdown properly may be because of that it can't be stopped using init script. Verify once again whether there is any nginx process running or port 80 is occupied. If you see any process is bind to port 80, Identify the PID and check if it can be killed. I had this problem, and running ps -ef grep nginx would show me workers that would keep spinning up, despite killing the master process as suggested by the accepted answer:.

My problem was that I had pid specified in two different conf files. After I removed one reference then deleted the. This seems to indicate that nginx is crashing immediately, if it had been started earlier. I'd need more information to be sure but, I'm guessing you already have another web server running rather than the instance of ngnix you want itself so you need to find it - the error says port 80 is in use, but not by what.

Try netstat -tulpn - You're looking for an entry under local address that ends with - this will also give you the program name and PID so you can identify it. Here's mine - I'm running lighttpd and its shown on the 3rd line. Shut down the other web server properly since if its spawning off upstart, a normal 'kill' may not work and try starting ngnix.

I had a similar issue with Ubuntu Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. It should be noted that the old master process does not close its listen sockets, and it can be managed to start its worker processes again if needed.

If for some reason the new executable file works unacceptably, one of the following can be done:. Send the HUP signal to the old master process. The old master process will start new worker processes without re-reading the configuration.

After that, all new processes can be shut down gracefully, by sending the QUIT signal to the new master process. Send the TERM signal to the new master process. It will then send a message to its worker processes requesting them to exit immediately, and they will all exit almost immediately. If new processes do not exit for some reason, the KILL signal should be sent to them to force them to exit.

When the new master process exits, the old master process will start new worker processes automatically. Posted By: Sandeep Agrawal August 16, About the error. Solution 1. First solution is to run command to generate missing file nginx.

Solution 2. Service command would timeout for Nginx. Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 2 years, 9 months ago. Active 2 days ago. Viewed 17k times. There is no reference to the PID in the nginx. Could anyone give me any pointers on how to troubleshoot or fix this please?

Improve this question. Add a comment. Active Oldest Votes. Reference Nginx server as forking process does support creating a PID file.