以前遇到一个问题: sudo /etc/init.d/apache2 start * Starting web server apache2 apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName ()Address already no listening sockets available, shutting down Unab…

**********************************************************处理办法:# ps -aux | grep httpWarning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.7/FAQroot     12079 0.0 0.0 61164   720 pts/1    S+   16:06   0:00 grep http# ps -aux | grep a…

netstat -tulpn| grep :80 killall -9 httpd /etc/init.d/httpd start  or service httpd start…

网上查了很多资料都是要杀进程,但是并没有找到占用的进程. 最后解决的方案是在apache配置文件下,去掉Listen 80 即可…

问题说明80端口被占用,用netstat -nlp |grep :80命令看看有什么进程占用了80端口,发现是httpd进程. 没想到安装了两个apache,我安装apache2.4的时候删除了2.2的apache啊, 可能是安装php memcache扩展的时候莫名其妙的安装了上了. 总之要卸载它 rpm -qa|grep -i httpd rpm -e --nodeps httpd-2.2.15-59.el6.centos.x86_64 rpm -e --nodeps httpd-tools…

说明80端口被用 终端:  ps -ef|grep httpd察看占用的进程或者用netstat -lnp|grep 80 找到后kill掉,如果都不行那么再试试以下方法(试过可以) 终端输入: find / -name ports.conf /etc/apache2/ports.conf 输入: vim '/etc/apache2/ports.conf' 键入‘i’即可修改, 将listen 80 这一句注释掉 按‘Esc’退出编辑状态 按‘:wq’,保存并退出(‘:q’不保存退出,‘:q!’…

# /etc/init.d/httpd startStarting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80no listening sockets available, shutting downUnable to open lo…

Apache启动时报错:(98)Address already in use: make_sock: could not bind to... # /etc/init.d/httpd start Starting httpd: ()Address already ()Address already no listening sockets available, shutting down Unable to open logs [FAILED] 1.查找占用80端口的进程,检查该进程是否能停用.…

在apache中绑定非http标准端口时,一直出现如下的错误提示: [root@localhost ~]# /etc/init.d/httpd start Starting httpd: (13)Permission denied: make_sock: could not bind to address 0.0.0.0:888 no listening sockets available, shutting down Unable to open logs [FAILED] 解决方案: 增加s…

CentOS 下启动Httpd 失败,报 (13)Permission denied: make_sock: could not bind to address [::]:8000 因为 小于1024 的端口只能是ROOT占用,但8000已经大于这个数值. Google 一下,发现原来是 SELinux  安全机制的作用. 查看一下预定义 #semanage port -l http_cache_port_t              tcp      3128, 8080, 8118, 112…