falha de httpd.service no Centos 7

Question

Estou enfrentando um problema com um VPS Centos 7 devido a um erro do apache:

quando eu faço:

[root@vm01 ~]# apachectl restart
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.

Com este erro de status:

[root@vm01 ~]# 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 Fri 2016-12-16 16:58:10 WET; 4min 41s ago
     Docs: man:httpd(8)
           man:apachectl(8)
  Process: 555 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
  Process: 553 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
 Main PID: 553 (code=exited, status=1/FAILURE)

Dec 16 16:58:10 vm01 systemd[1]: Starting The Apache HTTP Server...
Dec 16 16:58:10 vm01 systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Dec 16 16:58:10 vm01 kill[555]: kill: cannot find process ""
Dec 16 16:58:10 vm01 systemd[1]: httpd.service: control process exited, code=exited status=1
Dec 16 16:58:10 vm01 systemd[1]: Failed to start The Apache HTTP Server.
Dec 16 16:58:10 vm01 systemd[1]: Unit httpd.service entered failed state.
Dec 16 16:58:10 vm01 systemd[1]: httpd.service failed.

E impressão de periódicos:

[root@vm01 ~]# journalctl -xn
-- Logs begin at Fri 2016-12-16 12:41:32 WET, end at Fri 2016-12-16 17:04:46 WET. --
Dec 16 13:22:59 vm01.jarodmobile.com systemd[1]: Unit systemd-logind.service entered failed state.
Dec 16 13:22:59 vm01.jarodmobile.com systemd[1]: systemd-logind.service failed.
Dec 16 13:22:59 vm01.jarodmobile.com systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
Dec 16 13:22:59 vm01.jarodmobile.com systemd[1]: Starting Login Service...
-- Subject: Unit systemd-logind.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-logind.service has begun starting up.
Dec 16 13:22:59 vm01.jarodmobile.com systemd[1]: Listening on udev Kernel Socket.
-- Subject: Unit systemd-udevd-kernel.socket has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-udevd-kernel.socket has finished starting up.
-- 
-- The start-up result is done.
Dec 16 13:22:59 vm01.jarodmobile.com systemd[1]: Starting udev Kernel Socket.
-- Subject: Unit systemd-udevd-kernel.socket has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-udevd-kernel.socket has begun starting up.
Dec 16 13:22:59 vm01.jarodmobile.com systemd[1]: Listening on udev Control Socket.
-- Subject: Unit systemd-udevd-control.socket has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-udevd-control.socket has finished starting up.
-- 
-- The start-up result is done.
Dec 16 13:22:59 vm01.jarodmobile.com systemd[1]: Starting udev Control Socket.
-- Subject: Unit systemd-udevd-control.socket has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-udevd-control.socket has begun starting up.
Dec 16 13:22:59 vm01.jarodmobile.com systemd[1]: Starting udev Kernel Device Manager...
-- Subject: Unit systemd-udevd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-udevd.service has begun starting up.
Dec 16 13:22:59 vm01.jarodmobile.com systemd[1]: systemd-journald.service watchdog timeout (limit 3min)!

Eu tenho procurado a solução para isso, mas sem sorte. Você pode ajudar?

Atenciosamente, Jaime

    

Answer 1

A saída do journalctl que você postou é claramente inútil. Como é muito da informação de inicialização. Eu costumo usar journalctl -xe para trás. Se isso não mostrar nada de útil, você pode tentar procurar em seu log de erros do httpd, que deve conter algumas informações relevantes.