When installing munin, a error message is show about incorrect permission :
warning: user apache does not exist - using root
This come from munin-node, where there is this line :
%dir %attr(0775,apache,munin) /var/log/munin
if apache is not installed ( and that's not a unreasonable request ), then there is no apache user.
Which webserver are you using instead?
I don't, that's for munin-node, it doesn't need a webserver.
Munin-node is running as root already, isnt it?
Your files living in /var/log/munin/munin-node.log are 0644 root:root perms right?
Yes, munin-node is running as root, but there ill still be a bug in some case.
Let's say, i install munin-node as part as kickstart ( that's basically what I did, just replace kickstart by puppet default config for my servers ), and then /var/log/munin/ is root:root.
Now, if there is something ( like for example, the munin script ) that run as apache and that requires to have /var/log/munin/ to be apache:root, this will fail, because munin-node was installed first. in fact, depending on the order of installation, even by doing yum install munin munin-node, this could fail.
ANd if nothing require apache:root on the directory, then the package should not ask such permissions.
A quick solution would be to make the log on munin-node go in /var/log/munin-node, with root:root, and the /var/log/munin directory should be moved to munin rpm, with apache:root.
True, using /var/log/munin-node/ would make it simpler, but upstream does not have a configuration definition for splitting out node logs vs master logs.
Installing munin-node will not fail per se, regardless of order within yum. As you saw, it changes the permissions to root ownership if the user does not exist.
If you are not running munin-master, why would your apache-run script log to /var/log/munin/ at all? (Your paragraph 3 example above) This data should be dumped to /var/lib/munin/plugin-state/ or /var/lib/munin/[hostname]/*.rrd.
Nevermind, you can edit /etc/munin/munin-node.conf, log_file to a new directory.
That would simplify the issue considerably.
Scratch build, but see if this works out better for you:
(Munin owns /var/log/munin, and needs to be written to by both apache and munin users, permissions remain accordingly. Munin-node owns /var/log/munin-node and is 0755 root:root. Logrotate file for munin-node was adjusted as well.)
munin-2.0.9-3.fc18 has been submitted as an update for Fedora 18.
munin-2.0.9-3.fc17 has been submitted as an update for Fedora 17.
munin-2.0.9-3.fc16 has been submitted as an update for Fedora 16.
munin-2.0.9-3.el6 has been submitted as an update for Fedora EPEL 6.
munin-2.0.9-3.el5 has been submitted as an update for Fedora EPEL 5.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing munin-2.0.9-3.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
munin-2.0.9-3.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-3.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 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-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.