Hi Detlef,
Does bbproxy crash with error "Fatal Signal caught!" in the situation you describe?
We experience a same problem, no mather the order we put the two servers in.
Let me explain:
$BBHOME/bin/bbproxy --hobbitd --listen="ip" --bbdisplay=A:port,B:port --report=$MACHINE.bbproxy --no-daemon --pidfile=$BBSERVERLOGS/bbproxy.pid Is the line found in hobbitlaunch.cfg
If A goes down, bbproxy crashes
if B goes down, same thing
If I switch A,B. Same situation.
Regards,
Jef Jagers Systems Engineer Thomson CompuMark
Thomson Reuters
T +32 3 220 76 02
From: Detlef Stracke [mailto:Detlef.Stracke at mobilcom.de] Sent: woensdag, september 23, 2009 14:43 To: hobbit at hswn.dk Subject: [hobbit] bbproxy timeout
Hi list,
the command
$BBHOME/bin/bbproxy --hobbitd --bbdisplay=12.13.14.15,20.21.22.23 --report=$MACHINE.bbproxy --no-daemon --pidfile=$BBSERVERLOGS/bbproxy.pid
works verry well. Unfortunately if the fist ip is unreachable (hardware is down), the 2nd get no data from the bbproxy. If I change the order of the ip`s, everythings works fine.
Regards
Detlef