Hello Paolo,
Am Sat, 10 Aug 2019 22:21:42 +0200 schrieb Paolo Benvenuto <paolobe...@gmail.com>: > > 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. > > > > > The only thing I saw: /var/log/munin/munin-node.log had root:root owner, I > changed to munin:adm, but the service fails the same way. ok - the directory exists - thus the problem seems to be an access issue when the service is started via systemd. I could imagine an issue with any kind of sandboxing configured on your host. Maybe for a start: take a look at /etc/systemd/system/multi-user.target.wants/munin-node.service. There you can see the following execution parameters: PrivateDevices=false PrivateTmp=true ProtectHome=true ProtectSystem=full Please comment out all of them and check, whether the service still fails. (the above change modifies a file of the package - not a conffile - thus the change will get lost with the next package upgrade) If this fixes the issue, then please find out, which of the setting is causing the failure. If this does not fix the issue, then maybe you could think of any kind of sandboxing security feature, that you configured for this host or its virtualization provider? (selinux, apparmor, ...) Cheers, Lars
