Hi....
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.
Try adding "--no-ares" to the bbtest-net commandline in hobbitlaunch.cfg. Does that help ?
No, there is the part of the hobbitlaunch.cfg
[bbnet] ENVFILE /home/hobbit/server/etc/hobbitserver.cfg NEEDS hobbitd CMD bbtest-net --no-ares --report --ping --checkresponse LOGFILE $BBSERVERLOGS/bb-network.log INTERVAL 5m
If not, I'd like to see the output from
Here is it:
bbcmd bbtest-net --debug --ping --checkresponse 2005-05-23 14:03:12 Using default environment file /home/hobbit/server/etc/hobbitserver.cfg Aborted (core dumped)
because the gdb trace is so messed up I cannot figure out where the real problem happens.
I use "gdb bin/bbtest-net tmp/core" is it right ??
Regards, Alex
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
On Mon, May 23, 2005 at 02:11:25PM +0200, Alexander.Sprotte at eventim.de wrote:
If not, I'd like to see the output from
Here is it:
bbcmd bbtest-net --debug --ping --checkresponse 2005-05-23 14:03:12 Using default environment file /home/hobbit/server/etc/hobbitserver.cfg Aborted (core dumped)
Hrm, something funky going on with the option passing there. Try this instead:
- login as the hobbit user
- run "bbcmd" (this starts a sub-shell with all of the Hobbit environment defined).
- run "bbtest-net --debug --ping --checkresponse --no-ares"
Henrik
On Mon, May 23, 2005 at 02:11:25PM +0200, Alexander.Sprotte at eventim.de wrote:
because the gdb trace is so messed up I cannot figure out where the real problem happens.
I use "gdb bin/bbtest-net tmp/core" is it right ??
Perfectly correct, but there is something happening inside bbtest-net that messes up the call stack, so it is no longer possible to see what happened.
Henrik
participants (2)
-
Alexander.Sprotte＠eventim.de
-
henrik＠hswn.dk