Linux下启动httpd服务提示not bind to address
2014-03-27 19:12
459 查看
这几天在装Apache httpd服务后,启动httpd服务,报错如下:
Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using 0.0.0.0 for ServerName
(13)Permission denied: make_sock: could not bind to address [::]:88
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:88
no listening sockets available, shutting down
Unable to open logs [FAILED]
发现是SELinux在作怪,查看SElinux使用状态
#getenforce
Enforcing
SElinux未禁用。
1、临时禁用SELinux:
# setenforce 0
这样重启服务器之后,还是会启动SELinux;
备注:setenforce 1 临时启用SELinux
2、永久禁用:
打开服务器上的SELinux配置文件,默认为:/etc/selinux/config(还有/etc/sysconfig/selinux),内容如下:
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - SELinux is fully disabled.
SELINUX=enforcing
# SELINUXTYPE= type of policy in use. Possible values are:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
SELINUXTYPE=targeted
将上面的
SELINUX=enforcing 改为:SELINUX=disable 禁用SeLinux
然后启动httpd服务:
service httpd start
Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using 0.0.0.0 for ServerName
[ OK ]
Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using 0.0.0.0 for ServerName
(13)Permission denied: make_sock: could not bind to address [::]:88
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:88
no listening sockets available, shutting down
Unable to open logs [FAILED]
发现是SELinux在作怪,查看SElinux使用状态
#getenforce
Enforcing
SElinux未禁用。
1、临时禁用SELinux:
# setenforce 0
这样重启服务器之后,还是会启动SELinux;
备注:setenforce 1 临时启用SELinux
2、永久禁用:
打开服务器上的SELinux配置文件,默认为:/etc/selinux/config(还有/etc/sysconfig/selinux),内容如下:
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - SELinux is fully disabled.
SELINUX=enforcing
# SELINUXTYPE= type of policy in use. Possible values are:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
SELINUXTYPE=targeted
将上面的
SELINUX=enforcing 改为:SELINUX=disable 禁用SeLinux
然后启动httpd服务:
service httpd start
Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using 0.0.0.0 for ServerName
[ OK ]
相关文章推荐
- Linux下启动httpd服务提示not bind to address
- Linux 下安装 Apache 后启动提示 (98)Address already in use: make_sock: could not bind to address [::]:80
- apache2不能启动的解决办法(提示could not bind to address 0.0.0.0:80)
- Linux 启动 Apache 时报错:(98)Address already in use: make_sock: could not bind to address [::]:80
- 服务启动时log4j提示Could not bind factory to JNDI
- httpd 启动报错“”Permission denied: make_sock: could not bind to address [::]:80“”
- Linux 启动 Apache 时报错:(98)Address already in use: make_sock: could not bind to add
- [Apache]apache2不能启动的解决办法(提示could not bind to address 0.0.0.0:80)
- Apache2不能启动的解决办法(提示could not bind to address 0.0.0.0:80)
- Linux 启动 Apache 时报错:(98)Address already in use: make_sock: could not bind to add
- apache启动报错(98)Address already in use: make_sock: could not bind to address [::]:80
- Apache启动错误:could not bind to address[::]:443
- Ubuntu下apache启动出错:Permission denied: make_sock: could not bind to address
- AH00072: make_sock: could not bind to address [::]:443 Aphache启动报443端口占用
- Apache启动报错:could not bind to address [::]:443 解决办法
- myeclipse 启动服务时 提示“Address already in use:JVM_Bind:8080”
- apache启动报错# Address already in use: make_sock: could not bind to address [::]:80
- 启动Apache时出现:(OS 10048)通常每个套接字地址(协议/网络地址/端口)只允许使用一次。 : AH00072: make_sock: could not bind to address
- apache启动报错(98)Address already in use: make_sock: could not bind to...
- windows下启动apache报make_sock: could not bind to address [::]:443错误!