Red Hat Bugzilla – Bug 821204
Wrong ownership of /var/run/munin
Last modified: 2012-07-30 15:50:23 EDT
Description of problem:
The update to munin 1.4.7-3.el6 changed ownership of /var/run/munin from
munin:munin to root:root. This breaks the munin cron job (/etc/cron.d/munin),
as it is run as user munin, and munin-update wants to create a lock file
Every five minutes, I got an error mail saying:
Creating lock /var/run/munin/munin-update.lock failed: Permission denied
at /usr/share/perl5/vendor_perl/Munin/Master/Update.pm line 128
Workaround is easy: just 'chown munin:munin /var/run/munin' (or the
equivalent in Puppet, which is what I actually have done).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Enable EPEL on CentOS 6.2
2. yum install munin-1.4.7-3.el6
3. Wait five minutes, then check the mail sent to root.
A mail is sent to root with the error message show above.
No error mail should be sent.
Presumably, the line
in the "%files common" section in the spec file should specify that the
directory should be owned by user and group munin. In the 1.4.7-1 spec
file, that is done in the %files section for the "munin" package, but
that line was removed for 1.4.7-3, without moving the ownership setting
over to the "munin-common" package.
Ugh. Sorry about this.
I messed it up in my cleanup for several other bugs. ;(
Will get a new batch of updates out soon... karma and testing very welcome.
munin-1.4.7-4.fc17 has been submitted as an update for Fedora 17.
munin-1.4.7-4.fc16 has been submitted as an update for Fedora 16.
munin-1.4.7-4.fc15 has been submitted as an update for Fedora 15.
munin-1.4.7-4.el6 has been submitted as an update for Fedora EPEL 6.
munin-1.4.7-4.el5 has been submitted as an update for Fedora EPEL 5.
I did a brief test of updating to the -4 RPMs from Koji, and saw no ill
effects (i.e., that version seems to work properly).
I tried upgrading both from -1 and from -3. Upgrading from -1 restored
/etc/munin/plugins as intended, and in both cases I get proper ownership
of /var/run/munin. (All tests performed on CentOS 6.2 x86_64 with all
Thanks for the quick response!
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing munin-1.4.7-4.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Looks OK on F15, just I am not getting the update thru updates-testing. Karma added.
Just a side note - would it not be wise to consider a /var/www/munin/.htaccess a config file? It rewrites my changes on every update.. I may create a separate bug for that for sure, but it probably needs some discussion.
We could. Do file another bug on it so we can get it changed.
munin-1.4.7-5.fc17 has been submitted as an update for Fedora 17.
munin-1.4.7-5.fc16 has been submitted as an update for Fedora 16.
munin-1.4.7-5.fc15 has been submitted as an update for Fedora 15.
munin-1.4.7-5.el6 has been submitted as an update for Fedora EPEL 6.
munin-1.4.7-5.el5 has been submitted as an update for Fedora EPEL 5.
munin-1.4.7-5.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
munin-1.4.7-5.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
munin-1.4.7-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
munin-1.4.7-5.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
munin-1.4.7-5.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
Problem still persist in munin-1.4.7-5.fc16.noarch
chown root:munin /var/run/munin
chmod 775 /var/run/munin
solved the problem.
This might be another case of 834055