You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Konstantin Boyandin <li...@boyandin.name> on 2011/03/06 04:34:13 UTC

'Could not get next bucket brigade' error

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.

Thank you.
Sincerely,
Konstantin


Re: 'Could not get next bucket brigade' error

Posted by Kris Deugau <kd...@vianet.ca>.
Boyandin Konstantin wrote:
> 06.03.11, 20:00, "Nico Kadel-Garcia"<nk...@gmail.com>:
>>   But there is also the RPMforge release of subversion-1.6.15 at
>>   http://rpmrepo.org/RPMforge/. Enjoy, I put up that one (based on
>>   variious previous releases.) I'd urge you to upgrade, ASAP, for a lot
>>   of *other* reasons.
>
> Thanks, but the above repository doesn't provide 64-bit version of the package.

Not sure where you're looking, but you're missing something:

[kdeugau@lilbro ~]$ rpm -q subversion
subversion-1.6.15-0.1.el5.rfx
[kdeugau@lilbro ~]$ cat /etc/redhat-release
CentOS release 5.5 (Final)

(The .rfx in the release number indicates "RPMForge Extras" - packages 
that will overwrite the stock CentOS/RHEL ones.)

If you prefer to direct-download the package files yourself, they're all 
in here:

http://packages.sw.be/subversion/

-kgd

Re: 'Could not get next bucket brigade' error

Posted by Boyandin Konstantin <li...@boyandin.name>.
06.03.11, 20:00, "Nico Kadel-Garcia" <nk...@gmail.com>:

> On Sun, Mar 6, 2011 at 7:22 AM, Andy Levy <an...@gmail.com> wrote:
>  > On Sat, Mar 5, 2011 at 22:34, Konstantin Boyandin <li...@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
>  
>  Red Hat has published subversion-1.6.11 for RHEL 5.6, and you can grab
>  and recompile it from your nearest Red Hat SRPM mirror
>  (http://mirrors.kernel.org/redhat is pretty good.) CentOS 5.6 has been
>  taking a while to release, so it's not published for CentOS yet.

It looks like the optimal solution in case of CentOS 5.5

>  But there is also the RPMforge release of subversion-1.6.15 at
>  http://rpmrepo.org/RPMforge/. Enjoy, I put up that one (based on
>  variious previous releases.) I'd urge you to upgrade, ASAP, for a lot
>  of *other* reasons.

Thanks, but the above repository doesn't provide 64-bit version of the package.

Sincerely,
Konstantin

Re: 'Could not get next bucket brigade' error

Posted by Nico Kadel-Garcia <nk...@gmail.com>.
On Fri, Mar 18, 2011 at 10:50 AM, Stefan Sperling <st...@elego.de> wrote:
> On Fri, Mar 18, 2011 at 10:40:34AM -0400, Nico Kadel-Garcia wrote:
>> Rechecking my test environment, 1.6.16 builds well enough on RHEL
>> 5/CentOS 5 with just the version change. RHEL 6 is a *disaster*,
>> partly due swig integration. (RHEL 6 finally has a recent enough swig
>> and sqlite not to need the separate tarballs, but that code needs
>> graceful management.)
>>
>> The internal ".spec" structure in
>> http://svn.apache.org/repos/asf/subversion/trunk/packages/rpm/ is also
>> *very* dangerous. It replaces the user's own .rpmmacros, without
>> warning and without making a backup. This is hideous behavior. I'll
>> send along some patches for that ASAP.
>
> I agree that's hideous.
> Patches to the packages are welcome.
> The last serious update seems to have been in 2009.
>
> But have you looked at red hat's source RPMs? If RPMforge packages could
> be based on those, we might as well delete our own packages/rpm/ directory.
> Build scripts for most Subversion packages these days are maintained elsewhere.

I have!!! They only came out a month or so ago as part of RHEL 5.6,
and CentOS hasn't published 5.6 yet, so I've not been working with it
at home. I agree there's potential there: a lot of the RPMforge
weirdness was due to support for RHEL 4, which is now obsolete and
only on "extended support", so a rewrite of that package is
reasonable, but would take considerably longer. And RPMforge is at
least 4 minor releases ahead of RHEL, and it's going to get worse over
time, not better, so RPMforge is still the place to go.

I'm definitely recommending yanking the
http://svn.apache.org/repos/asf/subversion/trunk/packages/rpm/{rhel-3,rhel-4}
directories, those haven't worked in years. Let me spend a bit more
time on the rhel-5 version. I think I can make that one more sane.

Re: 'Could not get next bucket brigade' error

Posted by Stefan Sperling <st...@elego.de>.
On Fri, Mar 18, 2011 at 10:40:34AM -0400, Nico Kadel-Garcia wrote:
> Rechecking my test environment, 1.6.16 builds well enough on RHEL
> 5/CentOS 5 with just the version change. RHEL 6 is a *disaster*,
> partly due swig integration. (RHEL 6 finally has a recent enough swig
> and sqlite not to need the separate tarballs, but that code needs
> graceful management.)
> 
> The internal ".spec" structure in
> http://svn.apache.org/repos/asf/subversion/trunk/packages/rpm/ is also
> *very* dangerous. It replaces the user's own .rpmmacros, without
> warning and without making a backup. This is hideous behavior. I'll
> send along some patches for that ASAP.

I agree that's hideous.
Patches to the packages are welcome.
The last serious update seems to have been in 2009.

But have you looked at red hat's source RPMs? If RPMforge packages could
be based on those, we might as well delete our own packages/rpm/ directory.
Build scripts for most Subversion packages these days are maintained elsewhere.

Re: 'Could not get next bucket brigade' error

Posted by Nico Kadel-Garcia <nk...@gmail.com>.
On Fri, Mar 18, 2011 at 10:26 AM, Stefan Sperling <st...@elego.de> wrote:
> On Fri, Mar 18, 2011 at 10:13:00AM -0400, Nico Kadel-Garcia wrote:
>> On Fri, Mar 18, 2011 at 10:07 AM, Stefan Sperling <st...@elego.de> wrote:
>> > On Thu, Mar 17, 2011 at 11:33:41PM -0400, Nico Kadel-Garcia wrote:
>> >> The 1.6.16 has some minor build-structure changes that have broken the
>> >> SRPM's. I'm wondering if it's even worth pursuing, for environments
>> >> that don't rely on HTTP/HTTPS authentication, especially because I'm
>> >> such a long-standing deprecator of that approach. (This is because the
>> >> Linux and UNIX clients store the passwords for HTTP/HTTPS access in
>> >> clear text.)
>> >
>> > That's not a good reason to neglect a security update. There are folks who
>> > need the update. Not that you're obliged to provide one -- you're doing
>> > voluntary work, afterall. But I'd expect that a package maintainer to
>> > keep the entire userbase in mind. Not just those running particular setups.
>> > It's not as if a Subversion HTTP/HTTPS setup was an unsupported use case.
>>
>> You've a point, but enabling people to repeat the errors of
>> mishandling stored passwords is not that high on my priority list.
>
> Fair enough.
>
> I will stop recommending RPMforge packages until more responsible
> maintainers show up.

Oh, my. Let's not get *into* the reponsibility, shall we?

Rechecking my test environment, 1.6.16 builds well enough on RHEL
5/CentOS 5 with just the version change. RHEL 6 is a *disaster*,
partly due swig integration. (RHEL 6 finally has a recent enough swig
and sqlite not to need the separate tarballs, but that code needs
graceful management.)

The internal ".spec" structure in
http://svn.apache.org/repos/asf/subversion/trunk/packages/rpm/ is also
*very* dangerous. It replaces the user's own .rpmmacros, without
warning and without making a backup. This is hideous behavior. I'll
send along some patches for that ASAP.



>> And the creeping changes to the build structure are making it more awkward
>> to maintain. If 1.7.0 is coming out soon, I'm not clear it's worthy my
>> efforts to even bother with this minor release.
>
> 1.7.0 isn't coming out soon.
>

Re: 'Could not get next bucket brigade' error

Posted by Stefan Sperling <st...@elego.de>.
On Fri, Mar 18, 2011 at 10:13:00AM -0400, Nico Kadel-Garcia wrote:
> On Fri, Mar 18, 2011 at 10:07 AM, Stefan Sperling <st...@elego.de> wrote:
> > On Thu, Mar 17, 2011 at 11:33:41PM -0400, Nico Kadel-Garcia wrote:
> >> The 1.6.16 has some minor build-structure changes that have broken the
> >> SRPM's. I'm wondering if it's even worth pursuing, for environments
> >> that don't rely on HTTP/HTTPS authentication, especially because I'm
> >> such a long-standing deprecator of that approach. (This is because the
> >> Linux and UNIX clients store the passwords for HTTP/HTTPS access in
> >> clear text.)
> >
> > That's not a good reason to neglect a security update. There are folks who
> > need the update. Not that you're obliged to provide one -- you're doing
> > voluntary work, afterall. But I'd expect that a package maintainer to
> > keep the entire userbase in mind. Not just those running particular setups.
> > It's not as if a Subversion HTTP/HTTPS setup was an unsupported use case.
> 
> You've a point, but enabling people to repeat the errors of
> mishandling stored passwords is not that high on my priority list.

Fair enough.

I will stop recommending RPMforge packages until more responsible
maintainers show up.

> And the creeping changes to the build structure are making it more awkward
> to maintain. If 1.7.0 is coming out soon, I'm not clear it's worthy my
> efforts to even bother with this minor release.

1.7.0 isn't coming out soon.

Re: 'Could not get next bucket brigade' error

Posted by Nico Kadel-Garcia <nk...@gmail.com>.
On Fri, Mar 18, 2011 at 10:07 AM, Stefan Sperling <st...@elego.de> wrote:
> On Thu, Mar 17, 2011 at 11:33:41PM -0400, Nico Kadel-Garcia wrote:
>> The 1.6.16 has some minor build-structure changes that have broken the
>> SRPM's. I'm wondering if it's even worth pursuing, for environments
>> that don't rely on HTTP/HTTPS authentication, especially because I'm
>> such a long-standing deprecator of that approach. (This is because the
>> Linux and UNIX clients store the passwords for HTTP/HTTPS access in
>> clear text.)
>
> That's not a good reason to neglect a security update. There are folks who
> need the update. Not that you're obliged to provide one -- you're doing
> voluntary work, afterall. But I'd expect that a package maintainer to
> keep the entire userbase in mind. Not just those running particular setups.
> It's not as if a Subversion HTTP/HTTPS setup was an unsupported use case.

You've a point, but enabling people to repeat the errors of
mishandling stored passwords is not that high on my priority list. And
the creeping changes to the build structure are making it more awkward
to maintain. If 1.7.0 is coming out soon, I'm not clear it's worthy my
efforts to even bother with this minor release.

Re: 'Could not get next bucket brigade' error

Posted by Stefan Sperling <st...@elego.de>.
On Thu, Mar 17, 2011 at 11:33:41PM -0400, Nico Kadel-Garcia wrote:
> The 1.6.16 has some minor build-structure changes that have broken the
> SRPM's. I'm wondering if it's even worth pursuing, for environments
> that don't rely on HTTP/HTTPS authentication, especially because I'm
> such a long-standing deprecator of that approach. (This is because the
> Linux and UNIX clients store the passwords for HTTP/HTTPS access in
> clear text.)

That's not a good reason to neglect a security update. There are folks who
need the update. Not that you're obliged to provide one -- you're doing
voluntary work, afterall. But I'd expect that a package maintainer to
keep the entire userbase in mind. Not just those running particular setups.
It's not as if a Subversion HTTP/HTTPS setup was an unsupported use case.

Re: 'Could not get next bucket brigade' error

Posted by Nico Kadel-Garcia <nk...@gmail.com>.
On Thu, Mar 17, 2011 at 10:38 PM, Konstantin Boyandin
<li...@boyandin.name> wrote:
> 03/07/2011 02:24 AM, Nico Kadel-Garcia пишет:
>> On Sun, Mar 6, 2011 at 11:43 AM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
>>> Nico Kadel-Garcia wrote on Sun, Mar 06, 2011 at 09:00:15 -0500:
>>>> On Sun, Mar 6, 2011 at 7:22 AM, Andy Levy <an...@gmail.com> wrote:
>>>>> On Sat, Mar 5, 2011 at 22:34, Konstantin Boyandin <li...@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
>>>>
>>>> Red Hat has published subversion-1.6.11 for RHEL 5.6, and you can grab
>>>> and recompile it from your nearest Red Hat SRPM mirror
>>>> (http://mirrors.kernel.org/redhat is pretty good.) CentOS 5.6 has been
>>>> taking a while to release, so it's not published for CentOS yet.
>>>>
>>>> But there is also the RPMforge release of subversion-1.6.15 at
>>>> http://rpmrepo.org/RPMforge/. Enjoy, I put up that one (based on
>>>> variious previous releases.) I'd urge you to upgrade, ASAP, for a lot
>>>> of *other* reasons.
>>>
>>> 1.6.15 contains a known remote DoS which is fixed by the just-released 1.6.16.
>>
>> I'm trying to recompile 1.6.16 for RHEL 5 based environments. There's
>> a number of fiddly little changes in the configurations which break
>> the RPM compilation.
>>
>> The remote DDOS is HTTP/HTTPS related. If you use svn+ssh, which I
>> recommend for security reasons anyway, you're apparently not at risk
>> of it.
>
> I would appreciate the RPMs compilation instructions for the 1.6.16 - or
> the link to SRPM.
>
> Thanks in advance!
>
> Sincerely,
> Konstantin

The 1.6.15 SRPM's are at http://rpmrepo.org/RPMforge/. I've not spent
a lot of time on this, I'm in the midst of interviewing for a role
involving Debian support and setting up a Debian environment. (My
current contract ended recently.)

The 1.6.16 has some minor build-structure changes that have broken the
SRPM's. I'm wondering if it's even worth pursuing, for environments
that don't rely on HTTP/HTTPS authentication, especially because I'm
such a long-standing deprecator of that approach. (This is because the
Linux and UNIX clients store the passwords for HTTP/HTTPS access in
clear text.)

Re: 'Could not get next bucket brigade' error

Posted by Konstantin Boyandin <li...@boyandin.name>.
03/07/2011 02:24 AM, Nico Kadel-Garcia пишет:
> On Sun, Mar 6, 2011 at 11:43 AM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
>> Nico Kadel-Garcia wrote on Sun, Mar 06, 2011 at 09:00:15 -0500:
>>> On Sun, Mar 6, 2011 at 7:22 AM, Andy Levy <an...@gmail.com> wrote:
>>>> On Sat, Mar 5, 2011 at 22:34, Konstantin Boyandin <li...@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
>>>
>>> Red Hat has published subversion-1.6.11 for RHEL 5.6, and you can grab
>>> and recompile it from your nearest Red Hat SRPM mirror
>>> (http://mirrors.kernel.org/redhat is pretty good.) CentOS 5.6 has been
>>> taking a while to release, so it's not published for CentOS yet.
>>>
>>> But there is also the RPMforge release of subversion-1.6.15 at
>>> http://rpmrepo.org/RPMforge/. Enjoy, I put up that one (based on
>>> variious previous releases.) I'd urge you to upgrade, ASAP, for a lot
>>> of *other* reasons.
>>
>> 1.6.15 contains a known remote DoS which is fixed by the just-released 1.6.16.
> 
> I'm trying to recompile 1.6.16 for RHEL 5 based environments. There's
> a number of fiddly little changes in the configurations which break
> the RPM compilation.
> 
> The remote DDOS is HTTP/HTTPS related. If you use svn+ssh, which I
> recommend for security reasons anyway, you're apparently not at risk
> of it.

I would appreciate the RPMs compilation instructions for the 1.6.16 - or
the link to SRPM.

Thanks in advance!

Sincerely,
Konstantin

Re: 'Could not get next bucket brigade' error

Posted by Nico Kadel-Garcia <nk...@gmail.com>.
On Sun, Mar 6, 2011 at 11:43 AM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> Nico Kadel-Garcia wrote on Sun, Mar 06, 2011 at 09:00:15 -0500:
>> On Sun, Mar 6, 2011 at 7:22 AM, Andy Levy <an...@gmail.com> wrote:
>> > On Sat, Mar 5, 2011 at 22:34, Konstantin Boyandin <li...@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
>>
>> Red Hat has published subversion-1.6.11 for RHEL 5.6, and you can grab
>> and recompile it from your nearest Red Hat SRPM mirror
>> (http://mirrors.kernel.org/redhat is pretty good.) CentOS 5.6 has been
>> taking a while to release, so it's not published for CentOS yet.
>>
>> But there is also the RPMforge release of subversion-1.6.15 at
>> http://rpmrepo.org/RPMforge/. Enjoy, I put up that one (based on
>> variious previous releases.) I'd urge you to upgrade, ASAP, for a lot
>> of *other* reasons.
>
> 1.6.15 contains a known remote DoS which is fixed by the just-released 1.6.16.

I'm trying to recompile 1.6.16 for RHEL 5 based environments. There's
a number of fiddly little changes in the configurations which break
the RPM compilation.

The remote DDOS is HTTP/HTTPS related. If you use svn+ssh, which I
recommend for security reasons anyway, you're apparently not at risk
of it.

Re: 'Could not get next bucket brigade' error

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Nico Kadel-Garcia wrote on Sun, Mar 06, 2011 at 09:00:15 -0500:
> On Sun, Mar 6, 2011 at 7:22 AM, Andy Levy <an...@gmail.com> wrote:
> > On Sat, Mar 5, 2011 at 22:34, Konstantin Boyandin <li...@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
> 
> Red Hat has published subversion-1.6.11 for RHEL 5.6, and you can grab
> and recompile it from your nearest Red Hat SRPM mirror
> (http://mirrors.kernel.org/redhat is pretty good.) CentOS 5.6 has been
> taking a while to release, so it's not published for CentOS yet.
> 
> But there is also the RPMforge release of subversion-1.6.15 at
> http://rpmrepo.org/RPMforge/. Enjoy, I put up that one (based on
> variious previous releases.) I'd urge you to upgrade, ASAP, for a lot
> of *other* reasons.

1.6.15 contains a known remote DoS which is fixed by the just-released 1.6.16.


Re: 'Could not get next bucket brigade' error

Posted by Nico Kadel-Garcia <nk...@gmail.com>.
On Sun, Mar 6, 2011 at 7:22 AM, Andy Levy <an...@gmail.com> wrote:
> On Sat, Mar 5, 2011 at 22:34, Konstantin Boyandin <li...@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

Red Hat has published subversion-1.6.11 for RHEL 5.6, and you can grab
and recompile it from your nearest Red Hat SRPM mirror
(http://mirrors.kernel.org/redhat is pretty good.) CentOS 5.6 has been
taking a while to release, so it's not published for CentOS yet.

But there is also the RPMforge release of subversion-1.6.15 at
http://rpmrepo.org/RPMforge/. Enjoy, I put up that one (based on
variious previous releases.) I'd urge you to upgrade, ASAP, for a lot
of *other* reasons.

Re: 'Could not get next bucket brigade' error

Posted by Konstantin Boyandin <li...@boyandin.name>.
03/06/2011 06:22 PM, Andy Levy writes:
> On Sat, Mar 5, 2011 at 22:34, Konstantin Boyandin <li...@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

Re: 'Could not get next bucket brigade' error

Posted by Andy Levy <an...@gmail.com>.
On Sat, Mar 5, 2011 at 22:34, Konstantin Boyandin <li...@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.
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