Estou tendo problemas com o Apache. Acabei de instalar o Centos e quero criar meu próprio servidor web. Estou seguindo as instruções de "o servidor perfeito para centos 7.2" e me deparei com esse erro na minha máquina
[root@server01 /]# sudo systemctl start httpd
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
[root@server01 /]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2016-11-02 14:04:03 PDT; 14s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 30113 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 30065 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 30065 (code=exited, status=1/FAILURE)
Nov 02 14:04:01 server01.tcforwarding.com systemd[1]: Starting The Apache HTTP Server...
Nov 02 14:04:02 server01.tcforwarding.com httpd[30065]: [Wed Nov 02 14:04:02.346089 2016] [alias:warn] [pid 30065] AH00671: The Scri...Alias.
Nov 02 14:04:02 server01.tcforwarding.com httpd[30065]: AH00548: NameVirtualHost has no effect and will be removed in the next relea...nf:356
Nov 02 14:04:02 server01.tcforwarding.com httpd: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Nov 02 14:04:02 server01.tcforwarding.com systemd: httpd.service: main process exited, code=exited, status=1/FAILURE
Nov 02 14:04:02 server01.tcforwarding.com kill: kill: cannot find process ""
Nov 02 14:04:03 server01.tcforwarding.com systemd httpd.service: control process exited, code=exited status=1
Nov 02 14:04:03 server01.tcforwarding.com systemd: Failed to start The Apache HTTP Server.
Nov 02 14:04:03 server01.tcforwarding.com systemd: Unit httpd.service entered failed state.
Nov 02 14:04:03 server01.tcforwarding.com systemd: httpd.service failed.
Esta é uma amostra do meu arquivo vhost
Alguém por favor pode me ajudar a descobrir isso?
sudo netstat -nap | grep :80retornos em execução
[root@server01 /]# sudo netstat -nap | grep :80
tcp 0 0 192.168.0.22:56616 104.16.13.8:80 TIME_WAIT -
tcp 0 0 192.168.0.22:43882 151.101.193.69:80 ESTABLISHED 6833/firefox
tcp 0 0 192.168.0.22:37556 151.101.129.69:80 ESTABLISHED 6833/firefox
tcp 0 0 192.168.0.22:37722 151.101.65.69:80 ESTABLISHED 6833/firefox
tcp 0 0 192.168.0.22:47506 151.101.1.69:80 ESTABLISHED 6833/firefox
tcp 0 0 192.168.0.22:55722 54.225.161.140:80 ESTABLISHED 6833/firefox
tcp 0 0 192.168.0.22:40710 107.14.33.34:80 ESTABLISHED 6833/firefox
tcp 0 0 192.168.0.22:43884 151.101.193.69:80 ESTABLISHED 6833/firefox
tcp 0 0 192.168.0.22:39374 50.16.185.14:80 ESTABLISHED 6833/firefox
tcp 0 0 192.168.0.22:57408 104.16.12.8:80 ESTABLISHED 6833/firefox
tcp6 0 0 2605:e000:9290:cf:57260 2607:f8b0:4007:80c::443 ESTABLISHED 6833/firefox
tcp6 0 0 2605:e000:9290:cf:42280 2607:f8b0:4007:801:::80 ESTABLISHED 6833/firefox
tcp6 0 0 2605:e000:9290:cf:35994 2607:f8b0:4007:80c::443 ESTABLISHED 6833/firefox
tcp6 0 0 2605:e000:9290:cf:42210 2607:f8b0:4007:80b:::80 ESTABLISHED 6833/firefox
agora executando o mesmo comando depois de desligar o Firefox
[root@server01 /]# sudo netstat -nap | grep :80
tcp 0 0 192.168.0.22:39514 151.101.129.69:80 TIME_WAIT -
tcp 0 0 192.168.0.22:39516 151.101.129.69:80 TIME_WAIT -
tcp 0 0 192.168.0.22:57042 54.243.224.230:80 TIME_WAIT -
tcp 0 0 192.168.0.22:59396 104.16.12.8:80 TIME_WAIT -
tcp 0 0 192.168.0.22:39734 151.101.65.69:80 TIME_WAIT -
tcp 0 0 192.168.0.22:58596 104.16.13.8:80 TIME_WAIT -
tcp 0 0 192.168.0.22:39510 151.101.129.69:80 TIME_WAIT -
tcp 0 0 192.168.0.22:37124 96.6.122.178:80 TIME_WAIT -
tcp 0 0 192.168.0.22:39696 151.101.65.69:80 TIME_WAIT -
tcp 0 0 192.168.0.22:57710 54.225.161.140:80 TIME_WAIT -
tcp 0 0 192.168.0.22:47790 64.95.32.61:80 TIME_WAIT -
tcp6 0 0 2605:e000:9290:cf:33722 2607:f8b0:4007:80b::443 TIME_WAIT -
tcp6 0 0 2605:e000:9290:cf:53536 2607:f8b0:4007:801::443 TIME_WAIT -
tcp6 0 0 2605:e000:9290:cf:58196 2607:f8b0:4007:806:::80 TIME_WAIT -
tcp6 0 0 2605:e000:9290:cf:51876 2607:f8b0:4007:800::443 TIME_WAIT -
agora executando este comando novamente, systemctl status httpd.serviceainda encontro o mesmo erro
[root@server01 /]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2016-11-02 20:34:28 PDT; 9s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 17357 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 17343 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 17343 (code=exited, status=1/FAILURE)
Nov 02 20:34:27 server01.tcforwarding.com systemd[1]: Starting The Apache HTTP Server...
Nov 02 20:34:28 server01.tcforwarding.com httpd[17343]: [Wed Nov 02 20:34:28.202720 2016] [alias:warn] [pid 17343] AH00671: The Scr...Alias.
Nov 02 20:34:28 server01.tcforwarding.com httpd[17343]: AH00548: NameVirtualHost has no effect and will be removed in the next rele...nf:356
Nov 02 20:34:28 server01.tcforwarding.com httpd[17343]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Nov 02 20:34:28 server01.tcforwarding.com systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Nov 02 20:34:28 server01.tcforwarding.com kill[17357]: kill: cannot find process ""
Nov 02 20:34:28 server01.tcforwarding.com systemd[1]: httpd.service: control process exited, code=exited status=1
Nov 02 20:34:28 server01.tcforwarding.com systemd[1]: Failed to start The Apache HTTP Server.
Nov 02 20:34:28 server01.tcforwarding.com systemd[1]: Unit httpd.service entered failed state.
Nov 02 20:34:28 server01.tcforwarding.com systemd[1]: httpd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
O problema ainda está me impedindo de iniciar
Executando nmap 192.168.0.1retornos de comando
Starting Nmap 6.40 ( http://nmap.org ) at 2016-11-06 15:52 PST
Nmap scan report for server01.tcforwarding.com (192.168.0.1)
Host is up (0.000016s latency).
Not shown: 992 closed ports
PORT STATE SERVICE
21/tcp open ftp
25/tcp open smtp
53/tcp open domain
110/tcp open pop3
143/tcp open imap
993/tcp open imaps
995/tcp open pop3s
3306/tcp open mysql
Nmap done: 1 IP address (1 host up) scanned in 0.15 seconds
Por que a porta 80 ou a porta 443 não aparece?
Responder1
Você já está executando algo na porta 80. Este comando irá identificá-lo para você
sudo netstat -nap | grep ':80 .*LISTEN'
Responder2
Eu diria que use o nmap para ver quais serviços estão sendo executados e em qual porta. Um resultado do nmap se parece com isto ...
$ nmap 192.168.50.25
...
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
80/tcp open http <~ make sure service is http
443/tcp open https
Se algo diferente de http estiver usando a porta 80, você poderá alterar a configuração do Apache e apontá-lo para uma porta diferente ou alterar o serviço que está usando a porta 80 para uma porta diferente.Aqui está um guia para instalar o nmap
Responder3
primeiro você deve usar o comando:
netstat -natup |grep 80
você deve nos informar qual serviço está rodando, se a porta 80 for usada por outro serviço, você deve eliminá-lo.
se desta forma não conseguir resolver o problema, você pode verificar a permissão do httpd.conf, você deve verificar se existe o comando:
listen [::]:80
porque podemos saber o erro no seu syslog
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
às vezes esse problema é causado pelo ipv6, então você deve adicionar o comando no seu conf
listen [::]:80 ipv6only=off default_server;
então você pode reiniciar o serviço httpd