Unable to start nginx - failed to read pid from file /run/nginx.pid

November 7, 2014 59.4k views
tridnguyen
By:
tridnguyen

Hi,

I just created a brand new fedora box.

I then install nginx by running yum install nginx.

I tried to start nginx with the following commands:

$ systemctl enable nginx
$ systemctl restart nginx

However, I got the following error

Failed to read PID from file /run/nginx.pid: Invalid argument

And nginx is not running properly (going to the public IP address of the box does not return anything.

Does anyone know what I did wrong?

Log In to Comment
3 Answers
adrianwhitezer August 31, 2016

I'm curious, did you resolve this issue?

Reply
asb MOD November 7, 2014

That pid error is often simply caused by restarting Nginx when it isn't started in the first place. Though the init script should be smart enough to fall back from restart to start. So I don't think that's the real problem here. Check to see that Nginx is running and the port that it is listening on by running: netstat -plunt | grep nginx

On Fedora 20, firewalld is running by default. Have you opened port 80?

If the netstat output shows that it is running, then the firewall is most likely your problem. To open the port, run:

firewall-cmd --permanent --zone=public --add-service=http
systemctl restart firewalld.service
Reply
  • zhannideruguode November 9, 2015

    hi,just like you say,I try:netstat -plunt | grep nginx
    print like that:
    tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 2370/nginx: master

    tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 2370/nginx: master

    tcp6 0 0 :::80 :::* LISTEN 2370/nginx: master

    tcp6 0 0 :::443 :::* LISTEN 2370/nginx: master

    [root@iZ943xbvop0Z ssl]# firewall-cmd --permanent --zone=public --add-service=http
    FirewallD is not running

    [root@iZ943xbvop0Z ssl]# systemctl restart firewalld.service
    Failed to issue method call: Unit firewalld.service is masked.

    how to solve the problem?

  • whitestar February 3, 2018

    Thank you so much. This did the job

bbaassssiiee November 15, 2016

This is a known bug with a workaround.

https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1581864

Reply
Have another answer? Share your knowledge.