Package: munin-node Version: 1.2.0-1 Severity: normal Hello,
It appears that munin-node starts at S20 (defaults, presumably), while many of the services it queries are started later (apache for instance is S91). I happened to notice this because I am running munin-node on many systems, and only collecting the data at a single point with munin. One of the systems had to be rebooted, and when it came up, munin-node was queried before ntp was up, and the node choked and apparently died. Last log line was: ntpq: read: Connection refused ntpq: read: Connection refused Process Backgrounded and then nothing for an hour and a half, until I noticed and started it manually. Moving munin-node's start up to S92 or so would certainly fix this. Probably the long term fix is to make sure that child scripts can't kill the main munin-node daemon, but this will work around it until then. Thanks, and if you need more information, please let me know, -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686-smp Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO-8859-15) Versions of packages munin-node depends on: ii libnet-server-perl 0.87-2 An extensible, general perl server ii perl 5.8.4-6 Larry Wall's Practical Extraction ii procps 1:3.2.5-1 /proc file system utilities -- no debconf information -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
