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

FW: Repeatable svnsync failure on a particular revision

From: Jonathan Ashley <jonathan.ashley_at_praxis-his.com>
Date: Thu, 14 Feb 2008 14:19:10 +0000

>I'm using svnsync to back up a repository between two Windows 2003
>machines running "Apache/2.2.4 (Win32) SVN/1.4.3 DAV/2
>mod_auth_sspi/1.0.4 mod_ssl/2.2.4 OpenSSL/0.9.8e".
>
>This failed for me on a revision yesterday, giving the message
>
>svnsync: REPORT request failed on 'http://source-machine/svn/imp'
>svnsync: REPORT of 'http://source-machine/svn/imp': Could not read response body: An existing connection was forcibly closed by the remote host. (http://source-machine)
>
>The interesting aspect is that this failure was repeatable, and always
>occurred at the same point. When I looked at the transactions folder on
>the destination machine, I could see the size of the 'rev' file
>increasing as svnsync ran, but it always failed when rev got to 47971744
>bytes. (For context, the size of the incremental dump file for that
>revision is 56085661 bytes).
>
>In the Apache server log on the source machine, I see in each case a lot
>of PROPFINDs from the destination machine, finishing with:
>
>10.1.8.1 - project-svnowner [06/Feb/2008:15:21:07 +0000] "REPORT http://source-machine/svn/imp HTTP/1.1" 200 68622428
>
>with a timestamp approximately seven minutes before the last update to
>the 'rev' file. I guess this is the failing request.
>
>I don't think it's the size of the revision that is the problem - I've
>successfully used svnsync to transfer bigger ones anyway.
>
>This is a critical server and backup for me, so I've had to manually
>work around the problem now (svnadmin dump / load of the problem
>revision, followed by manual adjustment of the revision 0 revprops).
>However, if anyone has experienced anything similar, or has a theory
>about what the problem was, I'd like to hear it. I can also help
>investigate if needed.

I'm forwarding this to the dev list because

a) no-one replied on the users list - I don't think svnsync is
   used that widely,
b) it looks like it might be a developer-related issue,
c) it's happened to me again on a couple of subsequent revisions,

The transactions always fail when the rev file is getting near
to the 50M mark - not exactly the same for each failed revision,
but always the same for each attempted transaction when
trying to sync that revision.

I suspect the problem is with Apache rather than Subversion. Is
there any easy way I can narrow the fault to one or the other?

Regards,

--
Jon Ashley
This email is confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, be advised that you have received this email in error and that any use, disclosure, copying or distribution or any action taken or omitted to be taken in reliance on it is strictly prohibited. If you have received this email in error please contact the sender. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Praxis. 
Although this email and any attachments are believed to be free of any virus or other defect, no responsibility is accepted by Praxis or any of its associated companies for any loss or damage arising in any way from the receipt or use thereof. The IT Department at Praxis can be contacted at it.support_at_praxis-his.com.
Praxis High Integrity Systems Ltd:
Company Number: 3302507, registered in England and Wales
Registered Address: 20 Manvers Street, Bath. BA1 1PX
VAT Registered in Great Britain: 682635707
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-02-14 15:19:24 CET

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