03/06/2011 06:22 PM, Andy Levy writes:
> On Sat, Mar 5, 2011 at 22:34, Konstantin Boyandin <lists_at_boyandin.name> wrote:
>> Hello,
>>
>> Setup: there's a server where Subversion repository is located (working
>> via Apache backend), OS CentOS 5.5, Subversion installed as RPM
>> subversion-1.4.2-4.el5_3.1
>>
>> Client: Fedora 14, Subversion installed from RPM
>> subversion-1.6.15-1.fc14.x86_64
>>
>> Problem: until yesterday, everything was fine. Yesterday and from now
>> on, when I try to commit changes, I see messages like this on client side:
>>
>> $ svn commit -m "Test update"
>> Sending 05/0/sh05p2.lyx
>> Transmitting file data .svn: Commit failed (details follow):
>> svn: Server sent unexpected return value (500 Internal Server Error) in
>> response to PUT request for
>> '/books/!svn/wrk/03fb3e1c-cd66-4799-ad3d-3d68c5787936/private/Shamteran/05/0/sh05p2.lyx'
>>
>> On the server side, the following appears in Apache logs:
>> [error] [client xx.xx.xx.xx] Could not get next bucket brigade [500, #0]
>>
>> I have rebuilt the repository from scratch, loaded the yesterday's dump
>> (made prior to update that started to cause error), result is the same.
>>
>> I would appreciate advice on
>> - how to find the reason for the error
>> - how to fix it without creating a new repository from scratch and
>> losing all the history of changes so far
>>
>> Running fsfsverify.py against the several latest rev file resulted in
>> nothing.
>
> 2 points:
> 1) SVN 1.4.x is no longer supported.
CentOS/RHEL do follow the tradition of keeping very old versions in
their repositories. Unless absolutely unavoidable, I prefer not to
compile the software pieces manually, otherwise I will end building
almost everything from sources, with all the consequences.
> 2) This is an Apache error, not Subversion. It can happen on servers
> that don't even have Subversion installed. This may be relevant to
> your installation: https://bugzilla.redhat.com/show_bug.cgi?id=572932
Thanks, the whole issue was malfunctioning hypervisor + faulty router
device at the hoster's. As soon as they fixed the mentioned problems,
the eerie 'buckert brigade' error was gone.
Sincerely,
Konstantin
Received on 2011-03-11 16:50:34 CET