nginx启动[emerg] still could not bind()怎么解决

我们在nginx部署完毕后或者是在其他情况去启动的时候会碰见如

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] still could not bind()

这样的情况。

有图可知，就是该nginx其实已经启动了。端口号已经被占了。

可以自己利用这个命令

netstat -ntlp|grep 80
[root@iZbp14dsc6whvwbrlnufnwZ sbin]# netstat -ntlp|grep 80
tcp        0      0 0.0.0.0:8086            0.0.0.0:*               LISTEN      12009/java          
tcp        0      0 127.0.0.1:8005          0.0.0.0:*               LISTEN      12416/java          
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      30903/nginx: master 
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      12416/java      

查看80的端口是否占用（nginx默认80端口）

如果我们需要去启动的话，需要先去杀死进程：kill -9 端口号

然后重新启动：./nginx

es：

# 快速停止nginx
./nginx -s stop
# 完整有序的停止nginx，这个命令会等待所有请求结束后再关闭nginx
./nginx -s quit
#执行重载命令 ./nginx -s reload

本文来自互联网用户投稿，文章观点仅代表作者本人，不代表本站立场，不承担相关法律责任。如若转载，请注明出处。 如若内容造成侵权/违法违规/事实不符，请点击【内容举报】进行投诉反馈！