Munin cron unable to start on Ubuntu Server 14.04

Bug #1359563 reported by Lepe
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
munin (Debian)
Fix Released
Unknown
munin (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Installed munin in a fresh Ubuntu 14.04.1 LTS server.

Munin version: 2.0.19-3

munin-cron fails to start. Trying to start it manually (using munin user with command: /usr/bin/munin-cron --debug) crashes with the error:

"not a reference at /usr/share/perl5/Munin/Master/Utils.pm line 863"

Extra details about the setup is here:
http://serverfault.com/questions/620846/munin-not-creating-html-files-in-ubuntu-server-14-04

Related Debian Bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696981
Related Fedora Bug:
https://bugzilla.redhat.com/show_bug.cgi?id=955902

no longer affects: munin
Changed in munin (Debian):
status: Unknown → Confirmed
Changed in munin (Ubuntu):
status: New → Confirmed
status: Confirmed → New
Revision history for this message
Lepe (alepe-com) wrote :

I solved the problem but I'm not 100% sure what was the source of it. I tried many things to bring back the error without success. I suspect there was an -old- munin process hanging there. The server is a production server so I didn't restart it.

This is why I suspect that:
When I had the problem described above, I restarted munin as usual "/etc/init.d/munin restart" or "service munin restart" and also "munin-node". I even purge and reinstalled munin but the problem persisted.
Just few minutes ago, I copied from other server all the /etc/munin directory (with an older version of munin), so I killed all "munin" processes before trying again. After retrying, munin was working without issues. I thought it was something inside the configuration files but even replacing the munin directory with the previous one it worked without problem (after restarting all munin services and removing any munin process) .

Summary: I probably installed munin too soon, when the server was not properly set up. After munin failed, some process might have been running which prevented munin to work correctly. Killing all "munin" process may have solved the problem.

Changed in munin (Debian):
status: Confirmed → Fix Committed
Changed in munin (Debian):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in munin (Ubuntu):
status: New → Confirmed
Revision history for this message
Robie Basak (racb) wrote :

Based on the Debian bug I believe this was fixed in 15.04.

If you need a fix for an existing stable release, please comment with a justification against https://wiki.ubuntu.com/StableReleaseUpdates#When and complete steps 1 through 4 in https://wiki.ubuntu.com/StableReleaseUpdates#Procedure - and go ahead with all the steps if you can. Note that that SRU team would need to make a final decision.

Changed in munin (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.