----- Andrew Hydle <ahydle@gmail.com> wrote:
> I am running svn 1.1.4 on debian linux. My repo is using fsfs.
>
> Currently the repository is on version 175 but will not allow commits.
> The client dies with the following error:
>
> Error: REPORT request failed on '/repos/CMPLXQ/!svn/vcc/default'
> Error: REPORT of '/repos/CMPLXQ/!svn/vcc/default': Could not read
> chunk delimiter: Secure connection truncated (
> https://svn.amthinking.net )
>
> and the error logs show:
>
> [Fri Sep 29 08:42:06 2006] [error] [client 10.10.20.152 ] Provider
> encountered an error while streaming a REPORT response. [500, #0]
> [Fri Sep 29 08:42:06 2006] [error] [client 10.10.20.152 ] A failure
> occurred while driving the update report editor [500, #200002]
> [Fri Sep 29 08:42:06 2006] [error] [client 10.10.20.152 ] Can't read
> length line in file
> '/export/home1/apache/svn.amthinking.net/repositories/CMPLXQ/db/revs/169'
> [500, #200002]
>
>
> svnadmin recover doesnt do anything
> svnadmin dump 1:168 allows a clean dump but I cannot dump 169 through
> 175
>
> How can I clean this up ASAP and how can I prevent this from happening
> in the future? This is for a development project that has a deadline
> and I have several developers waiting.
1) You need to run 'svnadmin verify' against your repositories, and do it often. It would have found this problem before now.
2) Check out fsfsverify at:
http://www.szakmeister.net/fsfsverify/
If it doesn't work for you, or you need help, then post the bad revision somewhere and send me the link to it.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 29 20:17:42 2006