munin-node after update to Lucid still in /etc/rc*.d, invoked twice

Bug #574704 reported by ilf on 2010-05-03
This bug affects 2 people
Affects Status Importance Assigned to Milestone
munin (Ubuntu)
Chuck Short

Bug Description

Binary package hint: munin

With system upgrade from Karmic to Lucid, munin-node was upgraded from 1.2.6-13ubuntu3 to 1.4.4-1ubuntu1.

Now on boot, i get the following in /var/log/boot.log:

  Rather than invoking init scripts through /etc/init.d, use the service(8)
  utility, e.g. service S98munin-node start
  Since the script you are attempting to invoke has been converted to an
  Upstart job, you may also use the start(8) utility, e.g. start S98munin-node
  start: Unknown job: S98munin-node

There is a /etc/init/munin-node.conf for invoking it via Upstart.
There's also /etc/init.d/munin-node, a symlink to /lib/init/upstart-job.

It seems the problem are these symlinks to /etc/init.d/munin-node:


How to fix this error?
Can I just delete the symlinks in /etc/rc*.d?
Will upstart then still know to start it on boot?

Related branches

Daniel Hahler (blueyed) wrote :

Yes, you can delete the symlinks in /etc/rc?.d and it should still work.

As far as I can see, those symlinks should have been deleted during upgrade, but apparently this is missing.

You can also remove /etc/init.d/munin-node - but this is probably left there for compatibility (for when somebody still uses "invoke-rc.d").

Changed in munin (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Daniel Hahler (blueyed) wrote :

Chuck, you have converted it to an upstart job.
Can you fix this - or comment at least how it should get fixed?

Changed in munin (Ubuntu):
assignee: nobody → Chuck Short (zulcss)
ilf (ilf) wrote :

Thanks for the hint.
Indeed, it's still started by upstart and removing /etc/rc?.d and /etc/init.d/munin-node has no effect on this.
So there should probably be a postinst/postrm for at least /etc/rc?.d.

Chuck Short (zulcss) wrote :

Can you try the version in my ppa?


Changed in munin (Ubuntu):
status: Triaged → In Progress
ilf (ilf) wrote :

Since I deleted the files by hand, I'm probably not suited to see if it works now.

Mrten (bugzilla-ii) wrote :

I can help out here, I've still got two servers that I didn't touch after upgrade from hardy to lucid. However, I don't see a recent munin or munin-node in your PPA.

Mrten (bugzilla-ii) wrote :

Ahh, so you have FIVE PPA's.

apt-get upgraded, rebooted, no change.

root@lida:/var/log/munin# apt-cache policy munin-node
  Installed: 1.4.4-1ubuntu2
  Candidate: 1.4.4-1ubuntu2
  Version table:
 *** 1.4.4-1ubuntu2 0
        500 lucid/main Packages
        100 /var/lib/dpkg/status
     1.4.4-1ubuntu1 0
        500 lucid/main Packages

That's one server, want me to test something else on the other?

Chuck Short (zulcss) wrote :

Ok thanks for testing,

Can you test the version at


Launchpad Janitor (janitor) wrote :

This bug was fixed in the package munin - 1.4.5-1ubuntu2

munin (1.4.5-1ubuntu2) maverick; urgency=low

  * debian/rules: Remove sysvinit symlinks. (LP: #574704, LP: #616404)
  * debian/control: Add libwww-perl as a dependency. (LP: #454302)
 -- Chuck Short <email address hidden> Fri, 13 Aug 2010 12:54:34 -0500

Changed in munin (Ubuntu):
status: In Progress → Fix Released
J Bruni (jbruni) wrote :


Please take a look here:

I had to change the upstart config ar /etc/init/munin-node.conf so munin-node could start on reboot for me.

This happened in a VPS under OpenVZ running Ubuntu Server 10.04 LTS (Lucid Lynx).

Thank you.

Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in munin (Ubuntu Lucid):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers