As I said previously ... was fixed somehow before release of Karmic.
--
munin-node is not started during system boot
https://bugs.launchpad.net/bugs/442575
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in ubuntu.
--
This should be fixed in lucid already.
chuck
** Changed in: munin (Ubuntu)
Status: Incomplete = Fix Released
--
munin-node is not started during system boot
https://bugs.launchpad.net/bugs/442575
You received this bug notification because you are a member of Ubuntu
Server Team, which is
For me it also does not start at boot. It seems that munin-node is
started to early - before the network interfaces are ready - and then
fails if the address to bind to doesn't exist.
/etc/munin/munin-node.conf:
...
# Which address to bind to;
host 10.0.1.50
...
/var/log/munin/munin-node.log:
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
munin-node is not started during system boot
https://bugs.launchpad.net/bugs/442575
You received this bug notification because
Im not able to reproduce this. I just did an upgrade from jaunty to
karmic and munin-node started fine. You might have bigger issues here.
Please add your /var/log/munin/munin-node.log
Regards
chuck
** Changed in: munin (Ubuntu)
Status: New = Incomplete
--
munin-node is not started
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32997939/Dependencies.txt
--
munin-node is not started during system boot
https://bugs.launchpad.net/bugs/442575
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin
