Как убрать ошибку nginx Failed to read PID from file /run/nginx.pid: Invalid argument?

Nginx работает , но смущает ошибка :
#service nginx status

systemd[1]: Failed to read PID from file /run/nginx.pid: Invalid argument
systemd[1]: Started A high performance web server and a reverse proxy server.

# cat /run/nginx.pid

9953

ls -la /run/nginx.pid

-rw-r--r-- 1 root root 5 Jul 3 03:21 /run/nginx.pid

Или nginx не может найти перед запуском файл (после рестарта например), далее его создает и далее нормально стартует ?
В error.log - пусто .

Upd1:

service nginx status
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled)
Active: active (running) since Fri 2015-07-03 04:16:07 MSK; 28s ago
Process: 14261 ExecStop=/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile /run/nginx.pid (code=exited, status=0/SUCCESS)
Process: 14366 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Process: 14363 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Main PID: 14367 (nginx)
CGroup: /system.slice/nginx.service
├─14367 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
└─14379 nginx: worker process

Upd2:
После ребута машины проблема сама исчезла ....

Вопрос задан более трёх лет назад
16394 просмотра

5 комментариев

Подписаться 3 Оценить 5 комментариев

Пригласить эксперта

Ответы на вопрос 1

Сергей @Weidmann

в nginx.conf закоментируй pid /path;

Ответ написан более трёх лет назад

3 комментария

Кирилл Казаков @mausspb Автор вопроса

Закомментировал. Не помогло. pid там же создается.

Написано более трёх лет назад
Сергей @Weidmann

cat /etc/nginx/nginx.conf | head -n 50
tail -n 100 /path/to/nginx/error_log
journalctl -xe | tail -n 50

Написано более трёх лет назад
Кирилл Казаков @mausspb Автор вопроса

Сергей:
cat /etc/nginx/nginx.conf | head -n 50

user www-data;
pid /run/nginx.pid;

worker_processes auto;

error_log /var/log/nginx/error.log crit;

timer_resolution 100ms;
worker_rlimit_nofile 100000;

events {
worker_connections 20480;
use epoll;
}

http {
include mime.types;
default_type application/octet-stream;

log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent"';

sendfile on;
tcp_nopush on;
tcp_nodelay on;
server_tokens off;
reset_timedout_connection on;
keepalive_timeout 120;
ssl_session_cache shared:SSL:20m;
large_client_header_buffers 8 8k;
server_names_hash_bucket_size 128;

gzip off;
gzip_proxied any;
gzip_types text/plain application/atom+xml text/xml application/xml application/javascript application/x-javascript text/javascript text/css text/json application/json;
gzip_min_length 1024;
gzip_comp_level 9;

include vhost-default.inc.conf;
include vhosts.d/*.conf;
}

tail -n 100 /var/log/nginx/error.log

2015/07/03 03:17:26 [notice] 9491#0: signal process started
2015/07/03 03:17:50 [notice] 9526#0: signal process started
2015/07/03 03:17:59 [alert] 9261#0: unlink() "/run/nginx.pid" failed (2: No such file or directory)
2015/07/03 03:18:33 [notice] 9663#0: signal process started
2015/07/03 03:18:33 [error] 9663#0: open() "/run/nginx.pid" failed (2: No such file or directory)
2015/07/03 03:18:55 [notice] 9714#0: signal process started
2015/07/03 03:20:45 [notice] 9855#0: signal process started
2015/07/03 04:16:20 [notice] 14378#0: signal process started

journalctl -xe | tail -n 50

-- Unit systemd-readahead-done.timer has finished starting up.
--
-- The start-up result is done.
Jul 03 04:28:09 vsnginx systemd[1]: Starting Mail Transport Agent.
-- Subject: Unit mail-transport-agent.target has begun with start-up
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mail-transport-agent.target has begun starting up.
Jul 03 04:28:09 vsnginx systemd[1]: Reached target Mail Transport Agent.
-- Subject: Unit mail-transport-agent.target has finished start-up
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mail-transport-agent.target has finished starting up.
--
-- The start-up result is done.
Jul 03 04:28:09 vsnginx postfix/master[396]: daemon started -- version 2.11.3, configuration /etc/postfix
Jul 03 04:28:09 vsnginx systemd[1]: Started Tell that Container is started.
-- Subject: Unit vzfifo.service has finished start-up
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit vzfifo.service has finished starting up.
--
-- The start-up result is done.
Jul 03 04:28:09 vsnginx systemd[1]: Started Update UTMP about System Runlevel Changes.
-- Subject: Unit systemd-update-utmp-runlevel.service has finished start-up
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-update-utmp-runlevel.service has finished starting up.
--
-- The start-up result is done.
Jul 03 04:28:09 vsnginx agetty[286]: /dev/console: cannot get controlling tty: Operation not permitted
Jul 03 04:28:09 vsnginx agetty[286]: /dev/console: cannot set process group: Inappropriate ioctl for device
Jul 03 04:28:09 vsnginx systemd[1]: Startup finished in 1.096s.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
--
-- Kernel start-up required KERNEL_USEC microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 1096534 microseconds.

Написано более трёх лет назад