Bug 2417981

Summary: munin receiving data, but drawing empty graphs
Product: [Fedora] Fedora Reporter: customercare
Component: muninAssignee: Kim B. Heino <b>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 42CC: b, drjohnson1, ingvar, jvanek
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-12-01 15:32:41 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 customercare 2025-12-01 12:17:05 UTC 
After upgrading from F41 to F42 the munin server does receive data from the nodes,
but does not draw a graph. No error messages of any value in the logs.

Name        : munin-node
Version     : 2.0.76
Release     : 5.fc42

Name        : munin
Version     : 2.0.76
Release     : 5.fc42

Munin was running for 15 years on the server, could be a "oldformat" issue.

What can i test? ( Yes, i sure it gets data, i tcpdumped the collection )

Reproducible: Always
Comment 1 Kim B. Heino 2025-12-01 13:58:08 UTC 
Which logs did you check? Only thing changed is SELinux policy, so check it's log. And nginx/apache. Maybe test by disabling SELinux?
Comment 2 customercare 2025-12-01 14:32:11 UTC 
SEL is disabled, and was disabled before.
Comment 3 customercare 2025-12-01 15:32:41 UTC 
We can close this. After the F42 upgrade, the crond -> munin cronjob failed, because crond did not startup.

Maincause: crond

But, maybe you can answere something else:

it was necessary to add local_address to the munin config, because it was connecting via ipv6 instaed of ipv4 , like the last 15 years.

Any idea if that is caused by munin itself, or a NetworkManager device priority  issue?
Comment 4 Kim B. Heino 2025-12-02 09:33:40 UTC 
Munin RPM package switched from cron to munin.timer in year 2020. Simply remove cronjob and run "systemctl enable --now munin.timer".

My guess is that some other perl package upgrade switched to prefer-IPv6. Munin itself doesn't have any preference but it uses other perl packages for communication.