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
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
Server Team, which is
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
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
** 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
Server Team, which is subscribed to munin in ubuntu.
--
Ubuntu-server-bugs
** 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
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 zul...@ubuntu.com Fri,
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 zul...@ubuntu.com Fri,
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
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
** 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
Server Team, which is subscribed
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
** 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
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
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
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
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
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
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
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
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
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
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
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
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
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
26 matches
Mail list logo