[Bug 574704] [NEW] munin-node after update to Lucid still in /etc/rc*.d, invoked twice
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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 574704] Re: munin-node after update to Lucid still in /etc/rc*.d, invoked twice
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. -- 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 574704] Re: munin-node after update to Lucid still in /etc/rc*.d, invoked twice
Since I deleted the files by hand, I'm probably not suited to see if it works now. -- 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 216847] Re: sshd will not start at boot if ListenAddress is set, because network interface is not yet up
Three years and six releases later, this is still present :( -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/216847 Title: sshd will not start at boot if ListenAddress is set, because network interface is not yet up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/216847/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 374537] Re: Munin-node have a empty /etc/munin/plugins folder
same with 1.2.6-13ubuntu1 on a fresh up-to-date karmic. -- Munin-node have a empty /etc/munin/plugins folder https://bugs.launchpad.net/bugs/374537 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
