Impossible de start bind

Support Debian
,
Tags: #<Tag:0x00007f50a2aa94f8> #<Tag:0x00007f50a2aa93b8>
#1

Bonjour
quand j’essaye de restart bind9 celui-ci me dit que « named.service » failed
donc si quelqu’un a la solution?

gamma@raspberrypi:~ $ service bind9 restart

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
Authentication is required to restart 'named.service'.
Authenticating as: ,,, (gamma)
Password:
==== AUTHENTICATION COMPLETE ====
Job for named.service failed because the control process exited with error code.
See "systemctl status named.service" and "journalctl -xeu named.service" for details.

gamma@raspberrypi:~ $
#2

Bonjour,

c’est généralement une bonne idée de suivre les recommandations des messages d’erreur :smiley:
Donne nous le retour des 2 commandes indiquées, pour qu’on ait plus de détails (surtout la 2e)

PS: pour que ton bloc de texte soit formaté, il faut mettre trois backquotes sur une ligne vide au-dessus et sur une ligne en dessous du texte

#3 
gamma@raspberrypi:~ $ systemctl status named.service
× named.service - BIND Domain Name Server
     Loaded: loaded (/lib/systemd/system/named.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Tue 2024-05-28 17:05:28 BST; 9min ago
       Docs: man:named(8)
    Process: 990 ExecStart=/usr/sbin/named -f $OPTIONS (code=exited, status=1/FAILURE)
   Main PID: 990 (code=exited, status=1/FAILURE)
        CPU: 76ms

May 28 17:05:28 raspberrypi systemd[1]: named.service: Scheduled restart job, restart counter is at 5.
May 28 17:05:28 raspberrypi systemd[1]: Stopped named.service - BIND Domain Name Server.
May 28 17:05:28 raspberrypi systemd[1]: named.service: Start request repeated too quickly.
May 28 17:05:28 raspberrypi systemd[1]: named.service: Failed with result 'exit-code'.
May 28 17:05:28 raspberrypi systemd[1]: Failed to start named.service - BIND Domain Name Server.
gamma@raspberrypi:~ $

gamma@raspberrypi:~ $ journalctl -xeu named.service
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit named.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
May 28 17:05:28 raspberrypi systemd[1]: named.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit named.service has entered the 'failed' state with result 'exit-code'.
May 28 17:05:28 raspberrypi systemd[1]: Failed to start named.service - BIND Domain Name Server.
░░ Subject: A start job for unit named.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit named.service has finished with a failure.
░░
░░ The job identifier is 1454 and the job result is failed.
May 28 17:05:28 raspberrypi systemd[1]: named.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit named.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
May 28 17:05:28 raspberrypi systemd[1]: Stopped named.service - BIND Domain Name Server.
░░ Subject: A stop job for unit named.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit named.service has finished.
░░
░░ The job identifier is 1529 and the job result is done.
May 28 17:05:28 raspberrypi systemd[1]: named.service: Start request repeated too quickly.
May 28 17:05:28 raspberrypi systemd[1]: named.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit named.service has entered the 'failed' state with result 'exit-code'.
May 28 17:05:28 raspberrypi systemd[1]: Failed to start named.service - BIND Domain Name Server.
░░ Subject: A start job for unit named.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit named.service has finished with a failure.
░░
░░ The job identifier is 1529 and the job result is failed.

Ps: Merci pour l’astuce.

#4

Si tu le fais en root ou sudo journalctl -u named, est-ce que le résultat donne plus d’informations ?

Sinon, en lançant manuellement bind (sudo /usr/sbin/named -u bind), qu’est-ce que ça dit ?

#5

Salut,
C’est quoi le contenu de named.service ?