[Bug 574704] [NEW] munin-node after update to Lucid still in /etc/rc*.d, invoked twice
ilf
ilf at zeromail.org
Mon May 3 20:07:12 BST 2010
Public bug reported:
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:
/etc/rc0.d/K20munin-node
/etc/rc1.d/K20munin-node
/etc/rc2.d/S98munin-node
/etc/rc3.d/S98munin-node
/etc/rc4.d/S98munin-node
/etc/rc5.d/S98munin-node
/etc/rc6.d/K20munin-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?
** Affects: munin (Ubuntu)
Importance: Undecided
Status: New
--
munin-node after update to Lucid still in /etc/rc*.d, invoked twice
https://bugs.launchpad.net/bugs/574704
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in ubuntu.
More information about the Ubuntu-server-bugs
mailing list