This evening I was sitting down to finally make some updates and bug fixes to this very blog, when I ran into my first subversion "incident." I was trying to do a checkout from my repository, served over HTTPS from my Mac Mini. First I tried the 'svn update' from my laptop, then from my desktop. In both cases, I was getting a weird error about "secure connection truncated." When I looked in my Apache error_log, I found the following suspicious lines:
[Sun Aug 14 20:07:38 2005] [error] [client 192.168.0.15] Provider encountered an error while
streaming a REPORT response. [500, #0]
[Sun Aug 14 20:07:38 2005] [error] [client 192.168.0.15] A failure occurred while driving the
update report editor [500, #160010]
[Sun Aug 14 20:19:04 2005] [error] [client 192.168.0.15] No such string '7o' [500, #160010]
Obviously, I had no clue why this was happening--I didn't remember anything odd going on with my subversion server in the past few weeks. Then again, it has been so long since my last check-in that I'm not sure I could have remembered. So I searched a little bit for this business about the report editor and "no such string XX". I found a few newsgroup postings, but they all seemed to be dealing with specific cases. The subversion FAQ caused me some momentary panic when I read about how the "failure occurred while driving the update report editor" error might require me to rebuild apache and mod_svn from source. Some more reading and testing revealed that I was (thankfully) not suffering from this problem.
In the end, good old 'svnadmin recover' saved the day:
Doug-Fales-Computer:~doug$ svnadmin recover /Library/projects/ Repository lock acquired. Please wait; recovering the repository may take some time... Recovery completed. The latest repos revision is 16.I had to adjust some permissions (I had run svnadmin as a different user than the one that httpd uses to access my repository), but then everything ran great again.
I'm not sure if I should feel good about 'svnadmin recover' fixing the problem, or if I should be disappointed in a one-user, one-project subversion repository becoming corrupt for no apparent reason. :/
August 14th, 2005 at 04:19 PM Dude, you have a typo in this here "coment" form <---->s future inhabitant, Laura, just got back in town and she sounds enthusiastic about doing a little baby sitting for the beanster, should you so desire... On a different note, here is a biblical conundrum for you learned folks: How is it that all of the seven churches mentioned in the book of revelations are in modern day turkey, yet they are 98% muslim? What does Muhammed have over Jesus or Moses? I think forced prayer 5 times a day is a definite factor in their success. Nothing like constant practice to reinforce anything and everything... You never know, some think the success of the Mormons can be attributed to: http://en.wikipedia.org/wiki/Love_bombing
August 15th, 2005 at 05:16 AM Dude, thanks for pointing out the typo. It's fixed. Why are you asking me about the book of Revelation? I thought you were a disciple of Tom Cruise and L. Ron Hubbard? When are you coming over again to b.s. with us about this stuff? And we'll definitely give Laura a call if she comes with the Jeff Stamp of Approval. Tova loved the last two babysitters you sent our way.
August 16th, 2005 at 12:09 AM I gota agree with Jeff here on the bDB vs. FSFS thing. I recently switched over to FSFS after Antonio gave me endless shit about having to run svn recover ever five check-ins (serious). Haven't had a single problem since. Apparently the way svn uses bDB really isn't multi-user safe. Or safe at all. If you read the subversion site they sorta make it sound like bDB issue, but I find that rather hard to swallow. bDB has been around for so many years it feels more like user error, the user being the svn programmers. If your prupose in life is to design and develop the next generation respository, then why not deal with multi-user issues up front? Haveing a big red flashing warning up front saying "the bDB version works (sorta) only for single users" should have been a must. Instead it took for ever for them to admit it was pretty much completely borked. What is this religous stuff your yaking about Jeff?
August 16th, 2005 at 12:10 AM Doug, it owuld be great if you did line break detection and inserted <p> breaks. :-)
August 16th, 2005 at 07:40 AM doug, i have a 4 word explanation for your repository problem: kung fu dot bat.
August 16th, 2005 at 07:58 AM Cy, thanks for the suggestion. I'm actually considering switching this blog over to typo and just contributing new functionality there (to typo). I'm kind of attached to this old crappy blog though, since it represents my first ruby on rails learning experience...
August 17th, 2005 at 12:20 AM I was wondering how long it would take you to find my little hack.....