Nginx logs an error when started on a machine with a single CPU:
systemctl start nginx
systemctl status nginx
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2016-05-14 19:35:03 UTC; 2s ago
Process: 1303 ExecStop=/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile /run/nginx.pid (code=exited, status=0/SUCCESS)
Process: 1307 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Process: 1306 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Main PID: 1308 (nginx)
Tasks: 5 (limit: 512)
Memory: 3.1M
CPU: 81ms
CGroup: /system.slice/nginx.service
├─1308 nginx: master process /usr/sbin/nginx -g daemon on; master_process on
├─1309 nginx: worker process
├─1310 nginx: worker process
├─1311 nginx: worker process
└─1312 nginx: worker process
May 14 19:35:03 ngx systemd[1]: Starting A high performance web server and a reverse proxy server...
May 14 19:35:03 ngx systemd[1]: nginx.service: Failed to read PID from file /run/nginx.pid: Invalid argument
May 14 19:35:03 ngx systemd[1]: Started A high performance web server and a reverse proxy server.
Bumping the number of CPU available makes the error disappear. This is reproducible on VMs and containers.
Lastly, the PID file is properly created and matches the PID of the master process.
Nginx logs an error when started on a machine with a single CPU:
systemctl start nginx system/ nginx.service; enabled; vendor preset: enabled) /sbin/start- stop-daemon --quiet --stop --retry QUIT/5 --pidfile /run/nginx.pid (code=exited, status=0/SUCCESS) /usr/sbin/ nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS) /usr/sbin/ nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS) slice/nginx. service
systemctl status nginx
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/
Active: active (running) since Sat 2016-05-14 19:35:03 UTC; 2s ago
Process: 1303 ExecStop=
Process: 1307 ExecStart=
Process: 1306 ExecStartPre=
Main PID: 1308 (nginx)
Tasks: 5 (limit: 512)
Memory: 3.1M
CPU: 81ms
CGroup: /system.
├─1308 nginx: master process /usr/sbin/nginx -g daemon on; master_process on
├─1309 nginx: worker process
├─1310 nginx: worker process
├─1311 nginx: worker process
└─1312 nginx: worker process
May 14 19:35:03 ngx systemd[1]: Starting A high performance web server and a reverse proxy server...
May 14 19:35:03 ngx systemd[1]: nginx.service: Failed to read PID from file /run/nginx.pid: Invalid argument
May 14 19:35:03 ngx systemd[1]: Started A high performance web server and a reverse proxy server.
Bumping the number of CPU available makes the error disappear. This is reproducible on VMs and containers.
Lastly, the PID file is properly created and matches the PID of the master process.
Additional information:
# lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
# apt-cache policy nginx-core 0ubuntu0. 16.04.1 0ubuntu0. 16.04.1 0ubuntu0. 16.04.1 500 archive. ubuntu. com/ubuntu xenial-updates/main amd64 Packages dpkg/status 9.15-0ubuntu1 500 archive. ubuntu. com/ubuntu xenial/main amd64 Packages
nginx-core:
Installed: 1.10.0-
Candidate: 1.10.0-
Version table:
*** 1.10.0-
500 http://
100 /var/lib/
1.
500 http://
ProblemType: Bug 0ubuntu0. 16.04.1 ature: Ubuntu 4.4.0-22.39-generic 4.4.8
DistroRelease: Ubuntu 16.04
Package: nginx-core 1.10.0-
ProcVersionSign
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sat May 14 19:35:21 2016
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
SourcePackage: nginx
UpgradeStatus: No upgrade log present (probably fresh install)