SVN could not get next bucket brigade
I spent hours and hours on fixing a problem with our svn repository this week and finally found out it was the firewall.
Maybe this helps some people out there to save some time.
symptoms:
Suddenly we could not check in certain files. The checkin lasted at least 4 minutes.
On the client side we got the error:
svn: PUT request failed on '/repos/...' svn: PUT of '/repos/...': 500 Internal Server Error (https://svn.webmeisterei.com/)
And in the error.log of apache we found:
[Wed Dec 12 14:27:06 2007] [error] [client 194.183.146.178] Could not get next bucket brigade [500, #0]
Googling for svn bucket brigade made me think our repositry got corrupted by the last checkin.
svnadmin verify did not find any corruptions, and a dump and load revocery of the repository
did not help either.
In addition, defining svn:externals like this:
# # Create this file: svn propget svn:externals . > EXTERNALS.txt # Apply this file: svn propset svn:externals -F EXTERNALS.txt . # package1 https://svn.webmeisterei.com/repos/foo/package1/trunk simplejson http://svn.red-bean.com/bob/simplejson/tags/simplejson-1.7/simplejson
resulted on the following error when checking the directory in after applying the property:
At least one property change failed; repository is unchanged
solution
If you encounter one of these errors you might want to check if your firewall has something to do with it.
In our case the Intrusion Protection has matched patterns when commiting certain files and svn:externals properties.
Leave a Reply