Attached is the strace and TCP traffic...
Also note that the error message has changed:
0 [lo-03-02]~/software/openmpi/ompi-trunk|> svn up
svn: REPORT request failed on '/svn/ompi/!svn/vcc/default'
svn: REPORT of '/svn/ompi/!svn/vcc/default': Could not send request
body: Connection reset by peer (http://svn.open-mpi.org)
It looks like the (on-disk) repository is now corrupt, even though the
error message indicates that the problem is to be found at the server.
svn status doesn't find any problem.
This new error looks permanent (happens always), the other one (XML
parse error) happens once in a while (even on a fresh checked-out copy)
Malcolm Rowe wrote:
> On Mon, Sep 26, 2005 at 10:25:35AM -0400, Jeff Squyres wrote:
>>1 [lo-03-02]~/software/openmpi|> svn co
>>svn: REPORT request failed on '/svn/ompi/!svn/bc/7442/trunk'
>>svn: The REPORT request returned invalid XML in the response: XML parse
>>error at line 1: mismatched tag (/svn/ompi/!svn/bc/7442/trunk)
>>The problem is fairly repeatable -- a fresh "co" will work after 2-3
>>tries, but trying to "up" after a successful checkout will nearly
>>always result in the problem.
> I just tried to na´vely reproduce this using a copy of the Subversion
> 1.2.0 client, but I didn't manage to. Although I'm not storing my working
> copy on a network filesystem, I would have thought that the error message
> you're getting would have more to do with what the server was sending,
> rather than the filesystem of the client's wc.
> If your user can reproduce this at will, perhaps they could try capturing
> the network traffic between the client and server? (instructions at
> http://subversion.tigris.org/faq.html#ethereal). That should give a clue
> as to whether the client, or the server, is at fault.
Received on Mon Sep 26 18:50:31 2005
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org