Bug 593633

Summary:	Munin does not work out of the box
Product:	[Fedora] Fedora	Reporter:	Pierre-YvesChibon <pingou>
Component:	munin	Assignee:	Kevin Fenzi <kevin>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	11	CC:	ingvar, kevin
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-05-19 16:34:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pierre-YvesChibon 2010-05-19 11:20:05 UTC

Description of problem:
I just installed munin on a F-11 computer, did not change anything on the settings (I just checked they were as I used to have them) and I got an error from the cron job.


Version-Release number of selected component (if applicable):
munin-1.4.3-2.fc11.noarch
munin-node-1.4.3-2.fc11.noarch


How reproducible:
always

Steps to Reproduce:
1.yum install munin munin-node
2.service munin-node start
3.wait for the cron job
  
Actual results:
cron returns:
bind failed: Permission denied at /usr/lib/perl5/vendor_perl/5.10.0/Munin/Master/Update.pm line 162


Expected results:
see the graphs

Additional info:

Comment 1 Kevin Fenzi 2010-05-19 16:15:10 UTC

This looks like possibly a duplicate of bug 565254 ?

Can you look for selinux denials? Does it work in permissive mode?

Comment 2 Pierre-YvesChibon 2010-05-19 16:34:47 UTC

Indeed it is, sorry for not seeing this earlier I was on ssh and did not think to check for denials.

*** This bug has been marked as a duplicate of bug 565254 ***