je rencontre un problème lors de l’installation de munin-node (apt install munin-node) et, plus précisément, lors du démarrage de son service suite à cette simple installation.
Au moment de l’installation :
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
× munin-node.service - Munin Node
Loaded: loaded (/lib/systemd/system/munin-node.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Mon 2023-09-11 09:14:11 CEST; 11min ago
Docs: man:munin-node(1) ...
Process: 2442 ExecStartPre=/usr/bin/install -o munin -g munin -d /run/munin (code=exited, status=0/SUCCESS)
Process: 2443 ExecStart=/usr/sbin/munin-node --foreground $DAEMON_ARGS (code=exited, status=1/FAILURE)
Main PID: 2443 (code=exited, status=1/FAILURE)
CPU: 85ms
sept. 11 09:14:11 bookworm systemd[1]: munin-node.service: Main process exited, code=exited, status=1/FAILURE
sept. 11 09:14:11 bookworm systemd[1]: munin-node.service: Failed with result 'exit-code'.
sept. 11 09:14:11 bookworm systemd[1]: Failed to start munin-node.service - Munin Node.
sept. 11 09:14:11 bookworm systemd[1]: munin-node.service: Scheduled restart job, restart counter is at 5.
sept. 11 09:14:11 bookworm systemd[1]: Stopped munin-node.service - Munin Node.
sept. 11 09:14:11 bookworm systemd[1]: munin-node.service: Start request repeated too quickly.
sept. 11 09:14:11 bookworm systemd[1]: munin-node.service: Failed with result 'exit-code'.
sept. 11 09:14:11 bookworm systemd[1]: Failed to start munin-node.service - Munin Node.
journalctl -xeu munin-node.service
sept. 11 09:07:07 bookworm systemd[1]: Starting munin-node.service - Munin Node...
░░ Subject: L'unité (unit) munin-node.service a commencé à démarrer
░░ Defined-By: systemd
░░ ...
░░
░░ L'unité (unit) munin-node.service a commencé à démarrer.
sept. 11 09:07:07 bookworm systemd[1]: munin-node.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ ...
░░
░░ An ExecStart= process belonging to unit munin-node.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
sept. 11 09:07:07 bookworm systemd[1]: munin-node.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ ...
░░
░░ The unit munin-node.service has entered the 'failed' state with result 'exit-code'.
sept. 11 09:07:07 bookworm systemd[1]: Failed to start munin-node.service - Munin Node.
░░ Subject: L'unité (unit) munin-node.service a échoué
░░ Defined-By: systemd
░░ Support: ...
Le problème est-il connu ? Existe-t-il une solution ?
Quand je rencontre ce genre de problème et que je manque de données, j’essaie de lancer le service à la main avec la commande utilisée par systemD, en y ajoutant éventuellement des options de verbosité afin d’avoir plus de pistes.
Mon conseil est peut-être un peu vague, mais, au moment de la rédaction de ce message, je n’ai pas la moindre idée de ce qu’est munin.
ls -l /usr/sbin/munin-node
-rwxr-xr-x 1 root root 5953 21 mars 21:08 /usr/sbin/munin-node
perl -v
This is perl 5, version 36, subversion 0 (v5.36.0) built for x86_64-linux-gnu-thread-multi
(with 52 registered patches, see perl -V for more detail)
Copyright 1987-2022, Larry Wall
Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.
Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at https://www.perl.org/, the Perl Home Page.
Je ne comprends vraiment pas ce que les gens ont contre l’IPv6…
Encore que les gens critiquent systemD, j’arrive un peu à comprendre, c’est un monolithe modulaire, une usine à gaz simple et fiable (les oxymores sont là parce que je n’ai pas d’avis particulier dessus), mais je ne comprends pas pour l’IPv6.
