Summary: | net-analyzer/munin initscript should create working ownership/permissions for /run/munin | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | A. Person <tesoro302> |
Component: | Current packages | Assignee: | Sysadmin Bugs <sysadmin> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alarig, bes.internal, graaff |
Priority: | Normal | Keywords: | PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/gentoo/gentoo/pull/19982 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
A. Person
2015-10-09 14:26:39 UTC
Hi, 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? 1. net-analyzer/munin-2.0.43 ># stat /run/ >File: /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" 2. > 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? https://wiki.gentoo.org/wiki/OpenRC#tmpfiles.d Closing this bug because the tmpfiles.d file should cover this and has been present in all recent versions. |