Description of problem: see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669230 same happened for the first time tonight for me on Fedora: error: skipping "/var/log/munin/munin-node.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. Version-Release number of selected component (if applicable): munin-node-2.0.8-1.fc17.noarch How reproducible: happened tonight for the first time after updating to munin-node-2.0.8-1.fc17.noarch yesterday
same here on all systems running munin-node-2.0.8-1.fc17.noarch
/me too
munin-2.0.9-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/munin-2.0.9-2.fc18
munin-2.0.9-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/munin-2.0.9-2.fc17
munin-2.0.9-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/munin-2.0.9-2.fc16
munin-2.0.9-2.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/munin-2.0.9-2.el6
munin-2.0.9-2.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/munin-2.0.9-2.el5
Package munin-2.0.9-2.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing munin-2.0.9-2.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-13705/munin-2.0.9-2.el5 then log in and leave karma (feedback).
(In reply to comment #8) > Package munin-2.0.9-2.el5: > * should fix your issue, > * was pushed to the Fedora EPEL 5 testing repository, > * should be available at your local mirror within two days. > Update it with: > # su -c 'yum update --enablerepo=epel-testing munin-2.0.9-2.el5' Well, epel-testing is not one of the standard Fedora repositories. Do you have some instructions how to add this? TIA, wd.
I did: yum update --enablerepo=updates-testing munin-node I also wondered why there has been no message how to test in on Fedora 17.
munin-2.0.9-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
munin-2.0.9-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
munin-2.0.9-3.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/munin-2.0.9-3.el6
munin-2.0.9-3.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/munin-2.0.9-3.el5
munin-2.0.9-3.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
munin-2.0.9-3.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-2.0.9-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Re-opening. Now I get: error: munin-node:9 unknown option 'su' -- ignoring line error: munin-node:9 unexpected text on Scientific Linux and CentOS 5. $ rpm -q munin-node munin-node-2.0.9-3.el5.noarch
I can confirm that current munin-node EPEL Packages wrongfully contain su in it and hence logrotate fails every day.
Run this again: yum update --enablerepo=updates-testing munin-node Report what version you now have if you continue to have troubles. At the moment, that would be 2.0.10-1.
There is no updates-testing repository. But using epel-testing I can install 2.0.10-1.el5 and the bug seems to be fixed with 2.0.10-1.el5. Thanks. I am also closing the bug again.