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

Re: The REPORT request returned invalid XML in the response: XML parse

From: Dries Kimpe <Dries.Kimpe_at_wis.kuleuven.be>
Date: 2005-10-07 16:39:06 CEST

Unfortunately, I cannot access nor get details about the used proxy, but
 I did get confirmation that there is actually one. I think it is safe
to assume that the proxy is causing the problems.

So, the best solution probably is to avoid the proxy and use https (or
another port).


Malcolm Rowe wrote:
> On Mon, Sep 26, 2005 at 06:22:32PM +0200, Dries Kimpe wrote:
>>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.
> Why do you think that it might be a disk problem?
> All I can see from the trace is exactly what the error message says: the
> server appears to reset the connection. While a tcpdump or ethereal trace
> might shed some more light, it looks like it's nothing more complex than
> a network problem.
> Does your user have a transparent (broken) HTTP proxy between you and them,
> perhaps? (You'd have to trace the network connection at the server side
> and check where the connection was coming from, I think).
> Regards,
> Malcolm

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 7 16:38:28 2005

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.