Bugzilla – Bug 1193118
munin doesn't work anymore correct.
Last modified: 2021-11-29 16:40:22 UTC
2021/11/26-00:30:03 CONNECT TCP Peer: "[::ffff:127.0.0.1]:49514" Local: "[::ffff:127.0.0.1]:4949"
2021/11/26-00:30:03  Error output from diskstats:
2021/11/26-00:30:03  Error in tempfile() using template /var/lib/munin/plugin-state/nobody/XXXXXXXXXX: Could not create temp file /var/lib/munin/plugin-state/nobody/dQcMJJa1jk: Permission denied at /usr/lib/perl5/vendor_perl/5.34.0/Munin/Plugin.pm line 278.
2021/11/26-00:30:03  Service 'diskstats' exited with status 13/0.
/var/lib/munin/plugin-state/nobody is owned by munin:munin but munin tries to write as "nobody".
And the new "hardening" options for "munin-node.service" blocks several plugins from working. Especially all the ones for Rasperry Pi's. Don't know yet which of the options is on fault.
This was from https://build.opensuse.org/request/show/928142
I'll have a look
For me the changes in the .service file don't cause issues. @Thorsten: can you please share the list of plugins you have enabled?
@Wolfgang: I needed to install perl-CGI-Fast to get munin to work, which isn't on Factory
I use it on a Raspberry Pi with some Pi specific modules.
For me it works if I remove:
ProtectClock breaks pythons time module. Don't ask me why, the error handling of this plugins/python code is really bad and I couldn't find out what exactly.
But the munin plugins do not set the time...
RestrictRealtime: I assume they need exact timing for some hardware protocols.
Thanks. Can you please https://build.opensuse.org/package/show/home:jsegitz:branches:server:monitoring/munin a try? I removed it from the node service, that should be enough.
As for RestrictRealtime: That should restrict the ability to have workloads run as realtime. Strange that they need it, I'll have another look
I bet it's needed to allow the RPI modules to communicate via GPIO, this is time critical with various sensors.
(In reply to Johannes Segitz from comment #5)
> Thanks. Can you please
> monitoring/munin a try? I removed it from the node service, that should be
The change is identical to my local changes, so should work.