在nginx中遇到 [alert] kill(25903, 1) failed (3: No such process)错误解决方法
2018-11-24 11:07
330 查看
当nginx出现如下类似错误的时候,不要惊慌,首先看报错日志,为什么报错,再寻求解决办法。
nginx: [alert] kill(25903, 1) failed (3: No such process)
通过在nginx/sbin,目录下 运行命令 ./nginx ,可看到如下错误:
nginx: [emerg] bind() to 0.0.0.0:8090 failed (98: Address already in use)
这就很清楚了,说明nginx的监听端口:8090被占用了。那么再使用命令lsof -i 8090查看什么应用占用了端口。如果是无关紧要的应用,便可Kill -9 强制杀掉相关应用,以便nginx的使用。
然后,即可启动nginx了,
./nginx -s reload
相关文章推荐
- nginx: [alert] kill(1668, 1) failed (3: No such process)的解决办法及nginx服务常用命令总结
- nginx: [alert] kill(1668, 1) failed (3: No such process)的解决办法及nginx常用命令总结
- nginx: [alert] kill(2480, 10) failed (3: No such process)的解决办法
- nginx: [alert] kill(2480, 10) failed (3: No such process)的解决办法及nginx服务常用命令总结
- 解决 nginx: [alert] kill(189, 1) failed (3: No such process)
- nginx: [alert] kill(2094,1) failed (3: No such process)
- linux 下nginx 的安装重启的时候出现[alert] kill(646, 1) failed (3: No such process)
- nginx: [alert] kill(12268, 1) failed (3: No such process)
- nginx: [alert] kill(1022, 1) failed (3: No such process)
- nginx平滑重启过程中提示[alert] kill(2942, 1) failed (No such process)问题分析及解决方案
- Nginx 报错: nginx: [error] open() "/usr/local/nginx/logs/nginx.pid" failed (2: No such file or directory) 的解决方法
- nginx运行php"No input file specified"错误的解决方法
- Tiny6410开发板linux启动错误 /init: line 102: can't open /r/dev/console: no such file 的解决方法
- 升级gcc4.8 遇到 fatal error: gnu/stubs-32.h: No such file or directory 问题的解决方法
- Ubuntu 升级错误信息:mount: mounting none on /dev failed: no such device的解决办法
- Linux下Apache重启遇到No space left on device错误的解决方法
- 引用原因.NET下编译C++代码时出现fatal error C1083: 无法打开包含文件:“iostream.h”: No such file or directory错误的解决方法.
- PHP错误mysql_connect(): No such file or directory解决方法
- 访问SQLite数据库遇到no such table 错误的解决办法
- Qt编译错误“GL/gl.h:No such file or directory”的解决方法