Hi all at hobbit.list,
a new version is out and it's running fine...
But my Apache problem exists further.
I can not monitoring the Apache-Status.
If I into the configuration the following line insert:
xxx.xxx.xxx.xxx www.xxxxxxxxx.com # ssh http://www.xxxxxxx.com/xxxxx.htm apache=http://www.xxxxxxx.com/server-status?auto LARRD:*,apache:apache|apache1|apache2|apache3
then hobbit say's -> "BBTEST "red" Programm crashed Fatal signal caught!" But the LARRD graph for Apache its running but all other tests not!
Whats Wrong ???
I use Hobbit 4.0.3 on SuSE Linux 9.2
The gdb say's (bbtest-net)
#4 0x401a6d41 in raise () from /lib/tls/libc.so.6 #5 0x401a8529 in abort () from /lib/tls/libc.so.6 #6 0x0805ca12 in sigsegv_handler (signum=11) at sig.c:57 #7 <signal handler called>
#7544 0x4000d6ae in _dl_name_match_p () from /lib/ld-linux.so.2 Previous frame inner to this frame (corrupt stack?)
(bbgen)
#4 0x401a6d41 in raise () from /lib/tls/libc.so.6 #5 0x401a8529 in abort () from /lib/tls/libc.so.6 #6 0x0805ca12 in load_all_links () at links.c:130 #7 <signal handler called>
#7544 0x4000d6ae in _dl_name_match_p () from /lib/ld-linux.so.2 Previous frame inner to this frame (corrupt stack?)
Please help.....
Cheers...
Alexander Sprotte
Alexander Sprotte [mailto:alexander.sprotte at eventim.de]
On Mon, May 23, 2005 at 01:39:23PM +0200, Alexander.Sprotte at eventim.de wrote:
Hi all at hobbit.list,
a new version is out and it's running fine...
But my Apache problem exists further.
Yes, there are a couple of bugs that haven't been dealt with in 4.0.3 - because I decided that they were so specific to your setup that I wouldn't hold up the release any more.
then hobbit say's -> "BBTEST "red" Programm crashed Fatal signal caught!"
Try adding "--no-ares" to the bbtest-net commandline in hobbitlaunch.cfg. Does that help ?
If not, I'd like to see the output from
bbcmd bbtest-net --debug --ping --checkresponse
because the gdb trace is so messed up I cannot figure out where the real problem happens.
Regards, Henrik
On Mon, May 23, 2005 at 01:39:23PM +0200, Alexander.Sprotte at eventim.de wrote:
But my Apache problem exists further.
If I into the configuration the following line insert:
xxx.xxx.xxx.xxx www.xxxxxxxxx.com # apache=http://www.xxxxxxx.com/server-status?auto
then hobbit say's -> "BBTEST "red" Programm crashed Fatal signal caught!"
With some help from Alexander I got this sorted out - it appears to be a bug that triggers when the response to the server-status request is very large (> 32 KB data).
-- Henrik Storner
participants (2)
-
Alexander.Sprotte@eventim.de
-
henrik@hswn.dk