[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Unexplicable errors on checkout...

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-10-25 11:55:50 CEST

On Wed, Oct 24, 2001 at 10:40:46AM +0200, Sander Striker wrote:
> Hi,
>
> I am having trouble doing a fresh checkout. I discussed this
> yesterday on irc with both Ben and Greg. RADICS Peter was
> seeing the same issue, but it went away for him. I have tried
> with the M5 and the r294 tarball, both show the same problem
> (at different points in a checkout each time). I sent a log
> to Greg by mail (was quite large) after recompiling with neon
> debug output enabled (see libsvn_ra_dav/session.c).
>
> My guess is that the server update has something to do with it.
> It might be a good idea to update the server again, now child
> exit codes are properly detected.

I don't think so...

Daniel (Bagder) sent me an ethereal dump of traffic which exhibits this
problem. Funny thing is: it looks like a *client* problem.

[ as an side: on a checkout, we should only be using ras->sess, but it looks
  like we're using two sessions to checkout the repository. ]

What I saw was the *client* issuing FIN to the server just after sending a
GET request. FIN is sent when somebody closes the socket (or maybe
shutdown()). The server then responds with a FIN,ACK to close its end. Then
the client *reissues* the GET request over the same socket(!). The server
responds with RST, meaning "you doofus. that socket is closed. I'll just RST
(reset) your socket."

I haven't tracked it further than that, though. I should be able to find it
tomorrow.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:45 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.