-
Site web down
Bonjour tous le monde,
J'ai une grosse galère sur un site web et j'aimerais un coup de main car je ne sais pas bien interpréter les logs.
Le site web n'est plus accessible depuis un restart systemctl apache2.
Que dos je faire ?
Merci
-- The process' exit code is 'exited' and its exit status is 1.
Jan 06 10:43:08 www systemd[1]: apache2.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Jan 06 10:43:08 www systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: A start job for unit apache2.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit apache2.service has finished with a failure.
--
-- The job identifier is 1015397 and the job result is failed.
Jan 06 10:43:08 www sudo[16845]: pam_unix(sudo:session): session closed for user root
Jan 06 10:44:41 www sudo[17436]: thomas : TTY=pts/0 ; PWD=/etc/apache2/sites-enabled ; USER=root ; COMMAND=/bin/nano w
Jan 06 10:44:41 www sudo[17436]: pam_unix(sudo:session): session opened for user root by thomas(uid=0)
Jan 06 10:45:12 www sudo[17436]: pam_unix(sudo:session): session closed for user root
Jan 06 10:45:21 www sudo[17672]: thomas : TTY=pts/0 ; PWD=/etc/apache2/sites-enabled ; USER=root ; COMMAND=/bin/nano w
Jan 06 10:45:21 www sudo[17672]: pam_unix(sudo:session): session opened for user root by thomas(uid=0)
Jan 06 10:45:42 www sudo[17672]: pam_unix(sudo:session): session closed for user root
Jan 06 10:45:46 www sudo[17824]: thomas : TTY=pts/0 ; PWD=/etc/apache2/sites-enabled ; USER=root ; COMMAND=/bin/system
Jan 06 10:45:46 www sudo[17824]: pam_unix(sudo:session): session opened for user root by thomas(uid=0)
Jan 06 10:45:46 www systemd[1]: Starting The Apache HTTP Server...
-- Subject: A start job for unit apache2.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit apache2.service has begun execution.
--
-- The job identifier is 1015487.
Jan 06 10:45:46 www apachectl[17827]: Action 'start' failed.
Jan 06 10:45:46 www apachectl[17827]: The Apache error log may have more information.
Jan 06 10:45:46 www systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit apache2.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Jan 06 10:45:46 www systemd[1]: apache2.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Jan 06 10:45:46 www systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: A start job for unit apache2.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit apache2.service has finished with a failure.
-
quel est le journal que vous montrez dans votre message ?
regardez les journaux d'erreur dans /var/log/apache2.
-
Essayez ceci pour tester la configuration:
Une variante qui vous affiche la configuration effective après chargement des fichiers de conf:
Au cas où vous n'avez pas de logs dans /var/log/ vous pouvez interroger journalctl:
Code:
journalctl -u nginx.service --since today
-
C'était un problème de clé ssh, je regardais pas le bon log.
