* Paul Radford
> No, I consider it a bug that munin-node fails silently, without so much
> as an error message. I was only able to discover the cause via strace.
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.
> I know that that is not a package maintainer's bug, but that you might fix
> it in the same way as mldonkey was fixed, with an init script tweak:
> http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg16629.html
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.)
> I'm not troubled by more writes on the tmpfs.
Duh, of course. Thinko.
--
Tore Anderson
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
