nginx reload报错:[error] open() “/tmp/nginx.pid“ failed

最新推荐文章于 2024-01-29 17:49:41 发布
原创 最新推荐文章于 2024-01-29 17:49:41 发布 · 538 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文介绍了一种常见的nginx错误——在尝试重新加载配置时出现的文件不存在错误，并提供了一个简单的解决方案：通过指定nginx配置文件路径来启动nginx。
nginx: [error] open() “/run/nginx.pid“ failed (2: No such file or directory)
liangkk的博客
08-04 2255
nginx.pid文件，在刚安装的时候就是没有,其实在启动 nginx 时自动生成，里面存放的是 当前 nginx 住进程的PID ，nginx相关操作都与要调用这个文件。
[nginx] nginx.pid open failed
qubes的专栏
10-09 828
enviroment1 系统： Linux nginx -s reload // 重载Nginx配置 error /xxx/nginx/nginx.pid failed (no such file or directory) resolution 报错原因是 当前没有启动Nginx服务 nginx -s stop // 停止 (删除pid文件) nginx // 启动 enviroment2 系统：ios error nginx -s stop 执行报错 open “/usr/local/var/run/
nginx启动报错：nginx: [error] open() “/var/run/nginx/nginx.pid“ failed (2: No such file or directory) 的解决
热门推荐
qq_39244882的博客
09-02 2万+
问题： 　　重启虚拟机后，再次重启nginx会报错：nginx: [error] open() "/var/run/nginx/nginx.pid" failed (2: No such file or directory) 问题原因： 　　提示信息说明在/var/run/nginx/目录下找不到nginx.pid文件，解决方式有两种： 　　　　第一种方式：创建默认目录/var/run/nginx/； 　　　　第二种方式：修改nginx.conf文件，指定pid文件所在目录...
nginx open() “/var/run/nginx.pid“ failed
afterlife_union的博客
03-29 5254
nginx 启动错误排查
报错处理：nginx: [error] open() /var/run/nginx/nginx.pid failed
ouyangzhenxin的博客
10-01 7385
解决Linux上Nginx启动报错：nginx: [error] open() /var/run/nginx/nginx.pid failed (2: No such file or directory)嗨，大家好！今天我来分享一个我在运维过程中遇到的问题，关于Linux上Nginx启动时出现的“nginx: [error] open() /var/run/nginx/nginx.pid fail...
[root@yfw ~]# cd /www/wwwroot/szrengjing.com/chat/dist [root@yfw dist]# curl -I https://szrengjing.com/chat/index.html --http1.1 --insecure curl: (52) Empty reply from server [root@yfw dist]# openssl s_client -connect szrengjing.com:443 -servername szrengjing.com -quiet depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1 verify return:1 depth=1 C = US, O = Let's Encrypt, CN = R13 verify return:1 depth=0 CN = szrengjing.com verify return:1 ^C [root@yfw dist]# ls -l /www/server/panel/vhost/cert/szrengjing.com/ total 8 -rw------- 1 root root 3587 Oct 30 07:44 fullchain.pem -rw------- 1 root root 1703 Oct 30 07:44 privkey.pem [root@yfw dist]# tail -f /www/wwwlogs/szrengjing.com.error.log 2025/11/11 15:22:27 [error] 1187603#0: *722977 FastCGI sent in stderr: "PHP message: PHP Warning: file_get_contents(/www/wwwroot/szrengjing.com/themes/dianpu1/library/member_info.lbi): failed to open stream: No such file or directory in /www/wwwroot/szrengjing.com/includes/cls_template.php on line 165" while reading response header from upstream, client: 144.76.32.114, server: szrengjing.com, request: "GET /supplier.php?go=category&suppId=5&id=43&brand=&price_min=&price_max=&page=&sort=last_update&order=ASC HTTP/1.1", upstream: "fastcgi://unix:/tmp/php-cgi-53.sock:", host: "szrengjing.com" 2025/11/11 15:22:34 [error] 1187603#0: *722977 FastCGI sent in stderr: "PHP message: PHP Warning: file_get_contents(/www/wwwroot/szrengjing.com/themes/dianpu1/library/member_info.lbi): failed to open stream: No such file or directory in /www/wwwroot/szrengjing.com/includes/cls_template.php on line 165" while reading response header from upstream, client: 144.76.32.114, server: szrengjing.com, request: "GET /supplier.php?go=category&suppId=5&id=44&brand=&price_min=&price_max=&page=&sort=last_update&order=ASC HTTP/1.1", upstream: "fastcgi://unix:/tmp/php-cgi-53.sock:", host: "szrengjing.com" 2025/11/11 15:22:43 [error] 1187603#0: *722977 FastCGI sent in stderr: "PHP message: PHP Warning: file_get_contents(/www/wwwroot/szrengjing.com/themes/dianpu1/library/member_info.lbi): failed to open stream: No such file or directory in /www/wwwroot/szrengjing.com/includes/cls_template.php on line 165" while reading response header from upstream, client: 144.76.32.114, server: szrengjing.com, request: "GET /supplier.php?go=category&suppId=5&id=45&brand=&price_min=&price_max=&page=&sort=last_update&order=ASC HTTP/1.1", upstream: "fastcgi://unix:/tmp/php-cgi-53.sock:", host: "szrengjing.com" 2025/11/11 15:22:49 [error] 1187603#0: *722977 FastCGI sent in stderr: "PHP message: PHP Warning: file_get_contents(/www/wwwroot/szrengjing.com/themes/dianpu1/library/member_info.lbi): failed to open stream: No such file or directory in /www/wwwroot/szrengjing.com/includes/cls_template.php on line 165" while reading response header from upstream, client: 144.76.32.114, server: szrengjing.com, request: "GET /supplier.php?go=category&suppId=5&id=46&brand=&price_min=&price_max=&page=&sort=last_update&order=ASC HTTP/1.1", upstream: "fastcgi://unix:/tmp/php-cgi-53.sock:", host: "szrengjing.com" 2025/11/11 15:33:03 [error] 1187603#0: *735443 FastCGI sent in stderr: "PHP message: PHP Warning: file_get_contents(/www/wwwroot/szrengjing.com/themes/dianpu1/library/member_info.lbi): failed to open stream: No such file or directory in /www/wwwroot/szrengjing.com/includes/cls_template.php on line 165" while reading response header from upstream, client: 66.249.66.33, server: szrengjing.com, request: "GET /supplier.php?go=category&suppId=5&id=19 HTTP/1.1", upstream: "fastcgi://unix:/tmp/php-cgi-53.sock:", host: "szrengjing.com" 2025/11/11 20:41:30 [error] 1187603#0: *807976 FastCGI sent in stderr: "PHP message: PHP Notice: Constant ADMIN_PATH already defined in /www/wwwroot/szrengjing.com/data/config.php on line 29" while reading response header from upstream, client: 85.208.96.208, server: szrengjing.com, request: "GET /supplier/ HTTP/1.1", upstream: "fastcgi://unix:/tmp/php-cgi-53.sock:", host: "szrengjing.com" 2025/11/11 20:41:33 [error] 1187603#0: *807983 FastCGI sent in stderr: "PHP message: PHP Notice: Constant ADMIN_PATH already defined in /www/wwwroot/szrengjing.com/data/config.php on line 29" while reading response header from upstream, client: 85.208.96.208, server: szrengjing.com, request: "GET /supplier/privilege.php?act=login HTTP/1.1", upstream: "fastcgi://unix:/tmp/php-cgi-53.sock:", host: "szrengjing.com" 2025/11/11 21:28:29 [error] 1187603#0: *818561 FastCGI sent in stderr: "PHP message: PHP Notice: Constant ADMIN_PATH already defined in /www/wwwroot/szrengjing.com/data/config.php on line 29" while reading response header from upstream, client: 183.7.149.88, server: szrengjing.com, request: "GET /supplier/ HTTP/1.1", upstream: "fastcgi://unix:/tmp/php-cgi-53.sock:", host: "szrengjing.com", referrer: "https://szrengjing.com/apply_index.php" 2025/11/11 21:28:29 [error] 1187603#0: *818567 FastCGI sent in stderr: "PHP message: PHP Notice: Constant ADMIN_PATH already defined in /www/wwwroot/szrengjing.com/data/config.php on line 29" while reading response header from upstream, client: 27.46.125.46, server: szrengjing.com, request: "GET /supplier/privilege.php?act=login HTTP/1.1", upstream: "fastcgi://unix:/tmp/php-cgi-53.sock:", host: "szrengjing.com", referrer: "https://szrengjing.com/apply_index.php" 2025/11/11 21:46:28 [error] 1187603#0: *821544 open() "/www/wwwroot/szrengjing.com/.well-known/traffic-advice" failed (2: No such file or directory), client: 66.249.81.132, server: szrengjing.com, request: "GET /.well-known/traffic-advice HTTP/1.1", host: "szrengjing.com"
11-12
nginx -t && systemctl reload nginx ``` 再测： ```bash curl -k https://szrengjing.com --http1.1 ``` 如果这次返回 `200` → 说明原配置中有干扰项！ --- ## 总结：你现在的问题链条 ``` Client → TCP ...
nginx: [emerg] open() "/usr/local/nginx/logs/nginx.pid" failed (28: No space left on device)
06-23
如果磁盘空间不足，可能会导致 Nginx 无法成功创建此文件，从而引发错误 `failed to open pid file: no space left on device`[^1]。 以下是针对该问题的详细解决方案： #### 1. 检查磁盘空间 首先需要确认磁盘...
user www www; worker_processes auto; error_log /www/wwwlogs/nginx_error.log crit; pid /www/server/nginx/logs/nginx.pid; worker_rlimit_nofile 100000; stream { log_format tcp_format '$time_local|$remote_addr|$protocol|$status|$bytes_sent|$bytes_received|$session_time|$upstream_addr|$upstream_bytes_sent|$upstream_bytes_received|$upstream_connect_time'; access_log /www/wwwlogs/tcp-access.log tcp_format; error_log /www/wwwlogs/tcp-error.log; include /www/server/panel/vhost/nginx/tcp/*.conf; } events { use epoll; worker_connections 51200; multi_accept on; } http { include mime.types; types { application/font-sfnt ttf; font/truetype ttf; font/opentype otf; application/font-woff woff; application/font-woff2 woff2; } default_type application/font-sfnt; #include luawaf.conf; include proxy.conf; default_type application/octet-stream; server_names_hash_bucket_size 512; client_header_buffer_size 32k; large_client_header_buffers 4 32k; client_max_body_size 300m; sendfile on; tcp_nopush on; keepalive_timeout 60; tcp_nodelay on; fastcgi_connect_timeout 3000; fastcgi_send_timeout 3000; fastcgi_read_timeout 3000; fastcgi_buffer_size 64k; fastcgi_buffers 4 64k; fastcgi_busy_buffers_size 128k; fastcgi_temp_file_write_size 256k; fastcgi_intercept_errors on; gzip on; gzip_min_length 1k; gzip_buffers 4 16k; gzip_http_version 1.1; gzip_comp_level 2; gzip_types text/plain application/javascript application/x-javascript text/javascript text/css application/xml; gzip_vary on; gzip_proxied expired no-cache no-store private auth; gzip_disable "MSIE [1-6]\."; limit_conn_zone $binary_remote_addr zone=perip:10m; limit_conn_zone $server_name zone=perserver:10m; server_tokens off; access_log off; server { listen 888; server_name phpmyadmin; index index.html index.htm index.php; root /www/server/phpmyadmin; location ~ /tmp/ { return 403; } #error_page 404 /404.html; include enable-php.conf; location ~ .*\.(gif|jpg|jpeg|png|bmp|swf)$ { expires 30d; } # 修正后的字体配置块 location ~* \.(ttf|otf|woff2?)$ { # 在开头添加 access_log /www/wwwlogs/font_access.log; error_log /www/wwwlogs/font_error.log; # ... 其他配置 ... root /www/wwwroot/yinzhang.jinshelby.com; rewrite ^/xcx/font/(.*)$ /public/xcx/font/$ 1 break; # 关键 MIME 类型 types {} default_type application/font-sfnt; # CORS 头 add_header Access-Control-Allow-Origin * always; add_header Access-Control-Allow-Methods 'GET, OPTIONS' always; add_header Access-Control-Allow-Headers 'Range' always; add_header Access-Control-Expose-Headers 'Content-Length,Content-Range' always; # 缓存 expires 1y; add_header Cache-Control "public, max-age=31536000, immutable"; # 字节范围支持（安卓必需） add_header Accept-Ranges bytes; if ($ request_method = 'OPTIONS') { return 204; } } location ~ .*\.(js|css)?$ { expires 12h; } location ~ /\. { deny all; } access_log /www/wwwlogs/access.log; } include /www/server/panel/vhost/nginx/*.conf; } 现在完整配置按照你说的是这样的 , 但是保存报错: nginx version: nginx/1.20.2 nginx: [warn] duplicate extension "ttf", content type: "font/truetype", previous content type: "application/font-sfnt" in /www/server/nginx/conf/nginx.conf:27 nginx: [warn] duplicate extension "woff", content type: "application/font-woff", previous content type: "font/woff" in /www/server/nginx/conf/nginx.conf:29 nginx: [warn] duplicate extension "woff2", content type: "application/font-woff2", previous content type: "font/woff2" in /www/server/nginx/conf/nginx.conf:30 nginx: [emerg] "default_type" directive is duplicate in /www/server/nginx/conf/nginx.conf:37 nginx: configuration file /www/server/nginx/conf/nginx.conf test failed
07-05
在字体文件的 location 块中，使用 `add_header` 来设置 Content-Type 头，但这样并不标准（因为 Nginx 会根据文件扩展名自动设置 Content-Type）。更好的做法是确保全局的 MIME 类型已经包含了这些字体类型，然后...
[root@yfw yfw_szrengjing_com]# sudo systemctl status wp-im-server ● wp-im-server.service - WordPress IM WebSocket Server Loaded: loaded (/etc/systemd/system/wp-im-server.service; disabled; vendor preset: disabled) Active: active (running) since Thu 2025-11-13 17:49:02 CST; 3h 57min ago Main PID: 404867 (php) Tasks: 2 (limit: 23712) Memory: 25.6M CGroup: /system.slice/wp-im-server.service ├─404867 WorkerMan: master process start_file=/www/wwwroot/yfw_szrengjing_com/wp-content/plug> └─404868 WorkerMan: worker process none websocket://0.0.0.0:2121 Nov 13 17:49:02 yfw.szrengjing.com systemd[1]: Starting WordPress IM Server (Workerman)... Nov 13 17:49:02 yfw.szrengjing.com systemd[1]: wp-im-server.service: Can't open PID file /tmp/wp-im-serve> Nov 13 17:49:02 yfw.szrengjing.com systemd[1]: Started WordPress IM Server (Workerman). [root@yfw yfw_szrengjing_com]# sudo systemctl status wp-im-server ● wp-im-server.service - WordPress IM WebSocket Server Loaded: loaded (/etc/systemd/system/wp-im-server.service; disabled; vendor preset: disabled) Active: active (running) since Thu 2025-11-13 17:49:02 CST; 3h 58min ago Main PID: 404867 (php) Tasks: 2 (limit: 23712) Memory: 25.6M CGroup: /system.slice/wp-im-server.service ├─404867 WorkerMan: master process start_file=/www/wwwroot/yfw_szrengjing_com/wp-content/plug> └─404868 WorkerMan: worker process none websocket://0.0.0.0:2121 Nov 13 17:49:02 yfw.szrengjing.com systemd[1]: Starting WordPress IM Server (Workerman)... Nov 13 17:49:02 yfw.szrengjing.com systemd[1]: wp-im-server.service: Can't open PID file /tmp/wp-im-serve> Nov 13 17:49:02 yfw.szrengjing.com systemd[1]: Started WordPress IM Server (Workerman). lines 1-13/13 (END)...skipping... ● wp-im-server.service - WordPress IM WebSocket Server Loaded: loaded (/etc/systemd/system/wp-im-server.service; disabled; vendor preset: disabled) Active: active (running) since Thu 2025-11-13 17:49:02 CST; 3h 58min ago Main PID: 404867 (php) Tasks: 2 (limit: 23712) Memory: 25.6M CGroup: /system.slice/wp-im-server.service ├─404867 WorkerMan: master process start_file=/www/wwwroot/yfw_szrengjing_com/wp-content/plug> └─404868 WorkerMan: worker process none websocket://0.0.0.0:2121 Nov 13 17:49:02 yfw.szrengjing.com systemd[1]: Starting WordPress IM Server (Workerman)... Nov 13 17:49:02 yfw.szrengjing.com systemd[1]: wp-im-server.service: Can't open PID file /tmp/wp-im-serve> Nov 13 17:49:02 yfw.szrengjing.com systemd[1]: Started WordPress IM Server (Workerman). ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-13/13 (END)
最新发布
11-14
wp-im-server.service: Can't open PID file /tmp/wp-im-server.pid (yet?) ``` 这个警告是 **正常的**，因为： - Workerman 使用自己的进程管理机制（master + worker） - 它不通过 systemd 创建 `.pid` 文件 - ...
nginx: [error] open() “/usr/local/nginx/logs/nginx.pid“ failed (2: No such file or directory)
weixin_54514751的博客
03-08 8884
那nginx在启动时怎么知道已经有正在运行的Nginx了呢？当Nginx启动时，会先检测有没有nginx.pid文件，如果没有则创建一个，并把自身的pid写进去。如果检测到已经有了nginx.pid文件，但是nginx检测到并没有哪个进程的id和该文件中id值相同，那么pid指向的进程不存在，nginx会正常启动，并把本次启动的pid写入nginx.pid文件中，反之，如果检测到有nginx.pid文件，同时该pid指向的进程存在，则说明nginx服务已经存在，那么本次启动nginx服务会报错。
解决nginx: [error] open() ＂/usr/local/nginx/logs/nginx.pid＂ failed错误
m0_75034791的博客
01-29 983
解决nginx: [error] open() ＂/usr/local/nginx/logs/nginx.pid＂ failed错误
nginx报错 [error] open() “/run/nginx.pid“ failed 或 invalid PID number ““ in “/run/nginx.pid“
dorlolo的博客
01-11 2271
【代码】nginx报错 [error] open() "/run/nginx.pid" failed 或 invalid PID number "" in "/run/nginx.pid"
open() "/var/run/nginx/nginx.pid" failed 解决方法
08-15 179
在 /var/run 下创建文件夹nginx 转载于:https://www.cnblogs.com/pennshawn/p/7366100.html
nginx.pid打开失败以及失效的解决方案
gzh_coder的博客
01-02 800
nginx.pid文件存储的是Nginx的进程号，如图： 其存放位置可在创建Makefile文件时通过 –pid-path 命令设置 有时候nginx.pid文件或者所在目录会存在丢失的可能 所以当我们想要启动nginx时：/usr/local/nginx/sbin/nginx -s reload 就会报这种错： nginx: [error] open() "/var/run/nginx/nginx.pid" failed (2: No such file or directory) 解决方案： 创建
【Nginx】nginx.pid打开失败以及失效的解决方案，附Nginx常用命令
m0_57293204的博客
10-10 3161
nginx.pid打开失败以及失效的解决方案，附Nginx常用命令 nginx.pid打开失败读取失效或pid无效
nginx.pid" failed (2: No such file or directory)
HH_KELE的专栏
03-22 789
kill -9 ， 删除nginx的所有进程 nginx -c /etc/nginx/nginx.conf nginx -s reload nginx -s quit nginx lsof -i:80 yum install lsof lsof 查看端口使用情况
nginx -s reload时出现open() "/run/nginx.pid" failed (2: No such file or directory)错误
weixin_33756418的博客
09-07 751
解决办法： 　　找到你的nginx.conf的文件夹目录，比如我的为/etc/nginx/nginx.conf,然后运行这个　　nginx -c /etc/nginx/nginx.conf命令，　　再运行nginx -s reload，就可以了 转载于:https://www.cnblogs.com/sqdtss/p/9604621.html...
nginx: [error] open() “/var/run/nginx/nginx.pid“ failed (2: No such file or directory)
javaxueba的博客
12-04 9732
2. 如果您在启动 Nginx 时遇到该错误消息，可能是因为 `/usr/local/nginx/logs/` 目录不存在。您可以尝试手动创建该目录，并确保其拥有适当的权限。在 Nginx 配置文件中查找 `error_log` 和 `pid` 配置指令，并检查路径是否正确。请注意，上述命令的用户和组可能因您的系统而异。如果不确定，请参考您的 Nginx 配置文件中的用户和组设置。请尝试上述方法来解决这个问题。3. 如果找不到 pid 文件，您可以尝试在命令行中指定一个自定义的 pid 文件路径。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值