[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [hobbit] Connection problems with bbproxy
- To: <hobbit (at) hswn.dk>
- Subject: RE: [hobbit] Connection problems with bbproxy
- From: "Kasperowicz, Shaun (Contractor)" <shaun.kasperowicz (at) xo.com>
- Date: Tue, 9 Aug 2005 16:32:07 -0600
- Thread-index: AcWdKHLXPc8he5sHQ3eA27FjvZ55sAACEaeQ
- Thread-topic: [hobbit] Connection problems with bbproxy
I had already been using the --debug and --log-details options, but the
logs weren't telling me much. I went ahead and ran bbproxy with the
--no-daemon option that you mentioned, and I started seeing quite a bit
more info on screen, including what looked like successful connections:
2005-08-09 15:25:10 state 0: connecting to server
2005-08-09 15:25:10 Connecting to BBDISPLAY at 10.88.19.48
2005-08-09 15:25:10 state 1: connecting to server
2005-08-09 15:25:10 Connecting to BBDISPLAY at 10.88.19.48
2005-08-09 15:25:10 state 0: request sent
2005-08-09 15:25:10 state 1: sending to server
2005-08-09 15:25:10 state 0: cleanup
2005-08-09 15:25:10 state 1: request sent
2005-08-09 15:25:11 state 0: cleanup
I opened the BBDISPLAY web page, and what do you know, it's working!?
However it only seems to work when invoked with the --no-daemon switch,
which really has us puzzled. I'd like to get it working in daemon mode,
but I'm not sure what the issue is here.
Oh, and I am seeing SYN-ACK packets coming back from the BB server, but
after that there is nothing. I will get you the snoop files for both
machines asap, if you still want to see them.
Thanks Henrik
-Shaun
-----Original Message-----
From: Henrik Stoerner [mailto:henrik (at) hswn.dk]
Sent: Tuesday, August 09, 2005 2:20 PM
To: hobbit (at) hswn.dk
Subject: Re: [hobbit] Connection problems with bbproxy
On Tue, Aug 09, 2005 at 01:03:21PM -0600, Kasperowicz, Shaun
(Contractor) wrote:
> Well after some more snooping, we find that bbproxy never makes a
> complete tcp connection with the BB server. You can see several
> connection attempts, but they are never completed, and the data is
never sent from bbproxy to the BB server.
I assume what you see in the snoop are the outgoing SYN packets from the
proxy, but not SYN-ACK packets coming back from the BB server ?
Could you run snoop on both servers - the one running bbproxy and the BB
server at the same time ? I'd like to have a look at that traffic.
> The bbproxy never gets that far...as if it's doing something during
> the negotiation that our old BB server doesn't like, so it drops the
connections.
> I'm beginning to think that our BB1.8b clients and server are too old
> for us to use bbproxy with them. Is this possible? I'm not sure how
> far back Hobbit is compatible with BB.
It *should* work - I dont think there's been any change in the BB daemon
for a very long time. I haven't tested bbproxy with a 1.8b server, but I
don't know of anything that would make it fail like this.
There's really nothing special in the way bbproxy sets up the connection
to the BB server - it just invokes the standard "connect()" routine.
> Also, is there a way to make logging more verbose with bbproxy? That
> might help the troubleshooting.
Start bbproxy as a foreground process with debugging enabled. Run it
with all of the usual options, plus "--debug --no-daemon".
One thing I come to think of ... what's the MAXLINE setting on your BB
server (in the $BBHOME/src/bb.h file) ? bbproxy will combine status-
messages into combo-messages - if it ends up building larger messages
than your BB server can accept, they could end up being discarded. But
then you should see the message going over the wire ...
Henrik
To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk