Tore Anderson wrote:
When you yank out essential data from underneath dpkg, all bets are
off. Anyway, I cannot reproduce the silent failure you're describing:
[EMAIL PROTECTED] :) sudo /etc/init.d/munin-node start
Starting munin-node: FAILED!
The log brings more information:
2006/07/31-16:12:09 Couldn't open pid file "/var/run/munin/munin-node.pid"
[No such file or directory].
at line 268 in file /usr/share/perl5/Net/Server.pm
2006/07/31-16:12:09 Server closing!
That's munin-node 1.2.3-1, on Debian Woody.
That's what I get for setting log level to 0 in munin-node.conf (/var
mounted read-only), I guess. *slaps forehead*. I had been looking for a
stdout message, but again that's upstream's decision. Sorry.
The following patch was commited to SVN a while back:
Index: munin-node.init
===================================================================
--- munin-node.init (revision 999)
+++ munin-node.init (working copy)
@@ -65,6 +65,14 @@
start() {
log_daemon_msg "Starting Munin-Node"
+ # /var/run could be a tmpfs filesystem,
+ # make sure that the pidfile directory exists
+ PIDDIR=${PIDFILE%/*}
+ if [ ! -d "$PIDDIR" ]; then
+ mkdir "$PIDDIR"
+ chmod 0755 "$PIDDIR"
+ chown munin "$PIDDIR"
+ fi
if pidofproc -p $PIDFILE $DAEMON >/dev/null; then
log_progress_msg "started beforehand"
log_end_msg 0
I haven't actually tried it, but it looks correct to me. (Don't know
if this is how mldonkey was handled, though.)
Yes, that looks perfect and is similar to my own modification. Thanks.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
