Hi Henrik,
now the errors in the hobbitlaunch.log are gone but in bb-display.log are still there. And another strange thing - since I reenabled the bbdisplay this morning I didn't see any host at the hobbit server! Just the subpages and groups are there.
Regards,
Stefan Loos
<br><br><br>>From: henrik at hswn.dk (Henrik Stoerner)<br>>Reply-To:
hobbit at hswn.dk<br>>To: hobbit at hswn.dk<br>>Subject: Re: [hobbit]
bbdisplay problems after adding some new hosts<br>>Date: Wed, 11 May 2005
11:06:13 +0200<br>><br>>Could you try removing the
"HEARTBEAT" line from hobbitlaunch.cfg and<br>>see if things
run OK after that
?<br>><br>><br>>Regards,<br>>Henrik<br>><br>>On Wed, May
11, 2005 at 07:41:37AM +0000, Stefan Loos wrote:<br>> > Hi,<br>>
><br>> > yesterday I add some new hosts to my hobbit-server and
short after that<br>> > hobbit had some problems.<br>> > Here is
what hobbitlauch.log says:<br>> ><br>> > 2005-05-11 09:11:18
Heartbeat lost for task hobbitd, bouncing it<br>> > 2005-05-11
09:11:18 Task bbretest started with PID 4523<br>> > 2005-05-11
09:11:23 Heartbeat lost for task hobbitd, killing it<br>> > 2005-05-11
09:11:23 Task bbdisplay started with PID 4524<br>> > 2005-05-11
09:11:23 Task hobbitd terminated by signal 9<br>> > 2005-05-11
09:11:23 Task hobbitd started with PID 4525<br>> > 2005-05-11 09:11:23
Loading hostnames<br>> > 2005-05-11 09:11:23 Loading saved
state<br>> > 2005-05-11 09:11:23 Setting up network listener on
0.0.0.0:1984<br>> > 2005-05-11 09:11:23 Setting up signal
handlers<br>> > 2005-05-11 09:11:23 Setting up hobbitd
channels<br>> > 2005-05-11 09:11:23 Setting up logfiles<br>> >
2005-05-11 09:11:28 Task bbhistory started with PID 4527<br>> >
2005-05-11 09:11:28 Task bbenadis started with PID 4528<br>> >
2005-05-11 09:11:28 Task bbpage started with PID 4530<br>> >
2005-05-11 09:11:28 Task larrdstatus started with PID 4532<br>> >
2005-05-11 09:11:28 Task larrddata started with PID 4534<br>> >
2005-05-11 09:12:18 Task bbretest started with PID 4541<br>> >
2005-05-11 09:12:23 Task bbdisplay started with PID 4542<br>> >
2005-05-11 09:12:43 Heartbeat lost for task hobbitd, bouncing it<br>>
> 2005-05-11 09:12:48 Heartbeat lost for task hobbitd, killing it<br>>
> 2005-05-11 09:12:48 Task hobbitd terminated by signal 9<br>> >
2005-05-11 09:12:48 Task bbdisplay terminated by signal 15<br>>
><br>> > So I tried to find out which component causes the problem
and disabled<br>> > everything in hobbitlauch.cfg and reenabled one by
one.<br>> > I found out that everytime I enabled bbdisplay those
errors occour.<br>> > The bb-display.log looks like this:<br>>
><br>> > 2005-05-11 09:09:48 Whoops ! bb failed to send message -
timeout<br>> > 2005-05-11 09:09:48 hobbitd status-board not
available<br>> > 2005-05-11 09:09:53 Whoops ! bb failed to send
message - timeout<br>> > 2005-05-11 09:10:53 Whoops ! bb failed to
send message - timeout<br>> > 2005-05-11 09:10:53 hobbitd status-board
not available<br>> > 2005-05-11 09:11:23 Could not connect to
bbd at 10.207.193.41:1984 -<br>> > Connection refused<br>> >
2005-05-11 09:11:23 Whoops ! bb failed to send message - Connection
failed<br>> > 2005-05-11 09:11:23 hobbitd status-board not
available<br>> > 2005-05-11 09:11:23 Could not connect to
bbd at 10.207.193.41:1984 -<br>> > Connection refused<br>> >
2005-05-11 09:11:23 Whoops ! bb failed to send message - Connection
failed<br>> ><br>> > I also found some core files in ~server/tmp
but I'm pretty shure they came<br>> > from killing hobbit -
nevertheless I've run the gdb util:<br>> ><br>> > GNU gdb Red
Hat Linux (6.1post-1.20040607.52rh)<br>> > Copyright 2004 Free
Software Foundation, Inc.<br>> > GDB is free software, covered by the
GNU General Public License, and you are<br>> > welcome to change it
and/or distribute copies of it under certain<br>> >
conditions.<br>> > Type "show copying" to see the
conditions.<br>> > There is absolutely no warranty for GDB. Type
"show warranty" for details.<br>> > This GDB was configured
as "i386-redhat-linux-gnu"...Using host<br>> > libthread_db
library "/lib/tls/libthread_db.so.1".<br>> ><br>> >
Core was generated by `hobbitd --debug<br>> >
--pidfile=/var/log/hobbit/hobbitd.pid --restart=/usr/local/hobb'.<br>>
> Program terminated with signal 6, Aborted.<br>> > Reading symbols
from /lib/tls/libc.so.6...done.<br>> > Loaded symbols for
/lib/tls/libc.so.6<br>> > Reading symbols from
/lib/ld-linux.so.2...done.<br>> > Loaded symbols for
/lib/ld-linux.so.2<br>> > #0 0x00df4cef in raise () from
/lib/tls/libc.so.6<br>> > (gdb) bt<br>> > #0 0x00df4cef in
raise () from /lib/tls/libc.so.6<br>> > #1 0x00df64f5 in abort ()
from /lib/tls/libc.so.6<br>> > #2 0x08054126 in sigsegv_handler
(signum=11) at sig.c:57<br>> > #3 <signal handler
called><br>> > #4 0x00e46cac in mempcpy () from
/lib/tls/libc.so.6<br>> > #5 0x00e3a4d2 in
_IO_default_xsputn_internal () from /lib/tls/libc.so.6<br>> > #6
0x00e13527 in vfprintf () from /lib/tls/libc.so.6<br>> > #7
0x00e2f3dc in vsprintf () from /lib/tls/libc.so.6<br>> > #8
0x00e1a03d in sprintf () from /lib/tls/libc.so.6<br>> > #9 0x0804d7a4
in do_message (msg=0x9e0b3f8, origin=0x80554bb "") at<br>> >
hobbitd.c:1903<br>> > #10 0x0804fcb5 in main (argc=8, argv=0xbfff9084)
at hobbitd.c:2944<br>> > (gdb)<br>> ><br>> > Now I try to
find out which of the new hosts - and what test causes the<br>> >
problems...<br>> ><br>> > Regards,<br>> ><br>> >
Stefan Loos<br>> ><br>> ><br>> ><br>> > To
unsubscribe from the hobbit list, send an e-mail to<br>> >
hobbit-unsubscribe at hswn.dk<br>> ><br>>
><br>><br>>--<br>>Henrik Storner<br>><br>>To unsubscribe
from the hobbit list, send an e-mail
to<br>>hobbit-unsubscribe at hswn.dk<br>><br>><br>