Paul Vella (Contractor) wrote:
> Hi all,
>
>
>
> I’m getting an error partway through checking out a large project (the
> MapGuide project, at http://svn.osgeo.org/mapguide/). Partway through
> the checkout, the process aborts with error:
>
>
>
> /Report of ‘/mapguide/!svn/vcc/default’: 200 OK
> (http://svn.osgeo.org)/
>
> I can complete the checkout by doing an update.
>
> I usually use TortoiseSVN with our subversion repository on our local
> LAN, and have never had this issue, but our projects are never this big.
>
> I’ve tried the command line subversion client (Collabnet build
> 1.5.4.33841) twice and have not had this issue, so I think it’s a
> TortoisSVN bug.
Can't be: TSVN uses the svn library for everything network related.
The only things different between TSVN and the collabnet build
* TSVN is an UI app, the other is a console app:
most virus scanners leave console apps alone and don't interfere with
those network connections, while they do with UI apps.
* TSVN has SSPI authentication enabled, the Collabnet build does not:
make sure you don't have a proxy in between which uses SSPI
authentication and has that authentication time out.
> I did a trace using Wireshark and all I could see was that the 2^nd last
> packet was from my client machine and had the TCP FIN flag set,
> following which there was the final packet from the server.
that means that the server has requested to close the connection. Here's
how a tcp connection actually closes:
Host A <- data transfer -> Host B
Host A -- FIN, ACK ------> Host B
Host A <-- ACK ---------- Host B
Host A <-- FIN, ACK ------ Host B
Host A ----- ACK --------> Host B
So if TSVN sends the FIN and then only one more packet is exchanged,
that means that the repository server has closed the connection, not TSVN.
> Happy to provide any further info that might help and congrats on such a
> fine piece of software,
I can reproduce this here with the repo url you mentioned. But: I don't
always get the same error, I sometimes get:
Error: REPORT of '/mapguide/!svn/vcc/default': Could not read chunk
size: connection
Error: was closed by server (http://svn.osgeo.org)
and sometimes it even succeeds without problems. Maybe if you would try
more times with the collabnet client, you could get it to fail too.
I would suspect a problem with the repository (a bad file/revision) or
the repository server. If you google for "subversion report 200-ok"
you'll get a lot of hits indicating either a corrupt repository or bad
harddrives on the server side
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-11-21 10:59:50 CET