munin-node is not started during system boot

[Lupe Christoph]

Binary package hint: munin

Speculating: /etc/init.d/munin-node is a conffile, so it is not replaced with an upstart-compatible version during an upgrade to Karmic.

In any case, munin-node is not started during system boot. And so /var/run/munin is not created, and the munin cronjob falls on it's nose:

Creating lock /var/run/munin/munin-update.lock failed: No such file or directory
Creating lock /var/run/munin/munin-graph.lock failed: No such file or directory
Creating lock /var/run/munin/munin-html.lock failed: No such file or directory

I'm having a smiliar problem with bacula. See Bug #442125.

ProblemType: Bug
Architecture: amd64
Date: Sun Oct 4 22:56:02 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: fglrx
Package: munin-node 1.2.6-13ubuntu2
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: munin
Uname: Linux 2.6.31-11-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:3319): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:3433): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:3472): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:3432): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -12 and height 24
 (gnome-panel:3432): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.1/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window

[Chuck Short (zulcss)]

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

[Chuck Short (zulcss)]

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!

[Holger Mauermann (mauermann)]

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:
...
2009/12/15-22:19:41 MyPackage (type Net::Server::Fork) starting! pid(1580)
Binding to TCP port 4949 on host 10.0.1.50
2009/12/15-22:19:41 Can't connect to TCP port 4949 on 10.0.1.50 [Cannot assign requested address]
  at line 88 in file /usr/share/perl5/Net/Server/Proto/TCP.pm
2009/12/15-22:19:41 Server closing!
shutdown() on closed socket GEN0 at /usr/lib/perl/5.10/IO/Socket.pm line 294.
...

ifconfig:
...
br1 Link encap:Ethernet HWaddr 40:61:86:07:75:77
          inet addr:10.0.1.50 Bcast:10.0.1.255 Mask:255.255.255.0
          inet6 addr: fe80::4261:86ff:fe07:7577/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:2817 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1073 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:193564 (193.5 KB) TX bytes:304457 (304.4 KB)
...

[Lupe Christoph (lupe)]

What Holger is seeing is different from my problem. I have "host *" in /etc/munin/munin-node.conf, and more importantly, my problem was not restricted to Munin and was fixed somehow before release of Karmic.

I propose to close this bug and would like to ask Holger to open a new one. His problem is probably related to upstart sequencing.

[Holger Mauermann (mauermann)]

For me it works now. If I put "bridge_maxwait 0" in /etc/network/interfaces munin-node is started at boot. Seems to be related to bridge-utils and upstart...

[Chuck Short (zulcss)]

This should be fixed in lucid already.

chuck

[Lupe Christoph (lupe)]

As I said previously "... was fixed somehow before release of Karmic."