Hello Paolo,
Am Sat, 10 Aug 2019 16:10:38 +0200 schrieb Paolo Benvenuto <paolobe...@gmail.com>: > I killed munin-node, and then restarted the service. The log says: > > 2019/08/10-16:03:15 Munin::Node::Server (type Net::Server::Fork) starting! > pid(4573) > Resolved [*]:4949 to [::]:4949, IPv6 > Not including resolved host [0.0.0.0] IPv4 because it will be handled by > [::] IPv6 > Binding to TCP port 4949 on host :: with IPv6 > > ipv6?????????? This is fine: munin-node supports IPv4 and IPv6. Binding to an IPv6 port by default also means binding to the respective IPv4 port (see "/proc/sys/net/ipv6/bindv6only"). > sudo systemctl start munin-node.service ; journalctl -xe > > I get: > > ago 10 16:07:48 catho2 systemd[1]: Starting Munin Node... > -- Subject: L'unità munin-node.service inizia la fase di avvio > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- L'unità munin-node.service ha iniziato la fase di avvio. > ago 10 16:07:48 catho2 munin-node[10019]: Couldn't open log file > "/var/log/munin/munin-node.log" [No such file or directory]. at > /usr/share/perl5/Net/Server.pm line 209. > ago 10 16:07:48 catho2 systemd[1]: munin-node.service: Control process > exited, code=exited, status=2/INVALIDARGUMENT The problem with creating /var/log/munin/munin-node.log seems to be the culprit. The directory should habe been created by the systemd component "munin.tmpfile" during bootup. I am confused, that this directory is missing on your host. Do you have an idea? Cheers, Lars
