[Bug 574704] Re: munin-node after update to Lucid still in /etc/rc*.d, invoked twice
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/574704 Title: munin-node after update to Lucid still in /etc/rc*.d, invoked twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/574704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574704] Re: munin-node after update to Lucid still in /etc/rc*.d, invoked twice
Hello! Please take a look here: http://askubuntu.com/questions/66517/why-service-munin-node-does-not-run-at-start-up-reboot/66545#66545 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/574704 Title: munin-node after update to Lucid still in /etc/rc*.d, invoked twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/574704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574704] Re: munin-node after update to Lucid still in /etc/rc*.d, invoked twice
** Branch linked: lp:ubuntu/munin -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574704] Re: munin-node after update to Lucid still in /etc/rc*.d, invoked twice
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 ShortFri, 13 Aug 2010 12:54:34 -0500 ** Changed in: munin (Ubuntu) Status: In Progress => Fix Released -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574704] Re: munin-node after update to Lucid still in /etc/rc*.d, invoked twice
Ok thanks for testing, Can you test the version at https://edge.launchpad.net/~zulcss/+archive /server-lucid-bug-fixes. Thanks chuck -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574704] Re: munin-node after update to Lucid still in /etc/rc*.d, invoked twice
Ahh, so you have FIVE PPA's. apt-get upgraded, rebooted, no change. r...@lida:/var/log/munin# apt-cache policy munin-node munin-node: Installed: 1.4.4-1ubuntu2 Candidate: 1.4.4-1ubuntu2 Version table: *** 1.4.4-1ubuntu2 0 500 http://ppa.launchpad.net/zulcss/server-bug-fixes/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 1.4.4-1ubuntu1 0 500 http://nl.archive.ubuntu.com/ubuntu/ lucid/main Packages That's one server, want me to test something else on the other? -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574704] Re: munin-node after update to Lucid still in /etc/rc*.d, invoked twice
** Also affects: munin (Ubuntu Lucid) 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574704] Re: munin-node after update to Lucid still in /etc/rc*.d, invoked twice
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. -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574704] Re: munin-node after update to Lucid still in /etc/rc*.d, invoked twice
Can you try the version in my ppa? Thanks chuck ** Changed in: munin (Ubuntu) Status: Triaged => In Progress -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574704] Re: munin-node after update to Lucid still in /etc/rc*.d, invoked twice
Chuck, you have converted it to an upstart job. Can you fix this - or comment at least how it should get fixed? -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574704] Re: munin-node after update to Lucid still in /etc/rc*.d, invoked twice
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 ** Changed in: munin (Ubuntu) Importance: Undecided => Medium ** Changed in: munin (Ubuntu) Assignee: (unassigned) => Chuck Short (zulcss) -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs