Bug 708835

Upstream bug: http://munin-monitoring.org/ticket/887

munin-1.4.5-10 should resolve.

I just install munin-1.4.6-1.fc15.noarch (Fedora 15 i686, SELinux active), and directory '/var/run/munin/' was not created:
# rpm -V munin
5S.T.....  c /etc/munin/munin.conf
chybí       /var/run/munin
...T.....    /var/www/html/munin/definitions.html
...T.....    /var/www/html/munin/logo-h.png
...T.....    /var/www/html/munin/logo.png
...T.....    /var/www/html/munin/style.css
(chybí==missing)

Second light defect (lazy to create extra report;): munin RPM creates directory '/etc/munin/conf.d/', but initial config file '/etc/munin/munin.conf' specify at this place other directory: "includedir /etc/munin/munin-conf.d"

(In reply to comment #2)
> I just install munin-1.4.6-1.fc15.noarch (Fedora 15 i686, SELinux active), and
> directory '/var/run/munin/' was not created:

Have you rebooted since installing? The tmpfiles.d entry will only happen on boot. 

> Second light defect (lazy to create extra report;): munin RPM creates directory
> '/etc/munin/conf.d/', but initial config file '/etc/munin/munin.conf' specify
> at this place other directory: "includedir /etc/munin/munin-conf.d"

Fix commited, should be in next update.

(In reply to comment #3)
> (In reply to comment #2)
> > I just install munin-1.4.6-1.fc15.noarch (Fedora 15 i686, SELinux active), and
> > directory '/var/run/munin/' was not created:
> 
> Have you rebooted since installing? The tmpfiles.d entry will only happen on
> boot. 
> 
> > Second light defect (lazy to create extra report;): munin RPM creates directory
> > '/etc/munin/conf.d/', but initial config file '/etc/munin/munin.conf' specify
> > at this place other directory: "includedir /etc/munin/munin-conf.d"
> 
> Fix commited, should be in next update.

No, I not did reboot.
It would be meant Linux is as windos, where reboot is needed to all.
Or we are now a step closely towards them and reboot is needed?

But seriously - I think SELinux blocked directory creation, because cpio archive contain it; and at other F15/i686 machine with SELinux disabled /var/run/munin/ is created after is munin package installed. Thus selinux rules should enable directory creation (when it is possible, i ntt know, i'm not selinux guru)

You may have mislabeled files.  To correct them:
su -c 'restorecon -Rv /var'

See if https://admin.fedoraproject.org/updates/munin-1.4.6-4.fc15.1 resolves this for you.




-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

it could be problem cause - in meantime i reboot machine, and it itself forced system relabeling at start (and systemd according to /etc/tmpfiles.d/munin.conf did create /var/run/munin/). But due to restart i'm now not able uncover problem cause.

'rpm -qa|grep munin|xargs -r rpm -e' remove nearly all from installed packages (munin, munin-common, munin-node). Nearly all - what i only found was ~35 broken symlinks in /etc/munin/plugins/, pointing to corresponding files in /usr/share/munin/plugins/ (but /usr/share/munin* was removed) - these files were probably created by munin-node-configure in munin-node postinst script.

with at koji referenced munin-1.4.6-4.fc15.1, it seems /var/run/munin/ is created OK. But "includedir /etc/munin/munin-conf.d" is still bad, and munin-node uninstall not remove /etc/munin/plugins/* symlinks.

(In reply to comment #6)
> 'rpm -qa|grep munin|xargs -r rpm -e' remove nearly all from installed packages
> (munin, munin-common, munin-node). Nearly all - what i only found was ~35
> broken symlinks in /etc/munin/plugins/, pointing to corresponding files in
> /usr/share/munin/plugins/ (but /usr/share/munin* was removed) - these files
> were probably created by munin-node-configure in munin-node postinst script.

Please file a bug on this? 

> with at koji referenced munin-1.4.6-4.fc15.1, it seems /var/run/munin/ is
> created OK. But "includedir /etc/munin/munin-conf.d" is still bad, and
> munin-node uninstall not remove /etc/munin/plugins/* symlinks.

Yes, as noted the includedir will be fixed in the NEXT release, it's commited, but not yet pushed out. 
The other is a bug, please file it instead of posting to this closed bug and we can get it fixed? ;)