Ownership and permissions of /run/munin are reset/recreated upon reboot and do not work for me. chown munin:nginx and chmod g+x gets it working in my case. Can something similar be built into the initscript?
I'm using munin-2.0.25-r1.
This error just occured to me too.
Since /var/run is a tmpfs, it gets emptied on every reboot. It is owned by root, and the munin-cron job is running under user munin, so it get's a permission denied, when it tries to create the munin folder.
Something like this has to be run as root:
mkdir -p /var/run/munin && chown munin /var/run/munin
Correct permissions should already be set up via the tmpfiles service. This was already the case in munin-2.0.19-r2 at least. Perhaps you are not using this service?
># stat /run/
>Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
munin internaly do like:
>sudo -u munin mkdir <rundir from munin config>
and fail with
>"cannot create directory ‘/run/munin’: Permission denied"
> Correct permissions should already be set up via the tmpfiles service
What is this and how this intersects with munin?
(In reply to Vladimir Varlamov from comment #3)
> > Correct permissions should already be set up via the tmpfiles service
> What is this and how this intersects with munin?
Closing this bug because the tmpfiles.d file should cover this and has been present in all recent versions.