[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Vague error with subversion + apache22 + freebsd

From: Michael Zatopek <zatomic_at_dizzylabs.org>
Date: Fri, 4 Jun 2010 15:54:35 -0500

On Jun 4, 2010, at 3:36 PM, Bruce A. Mah wrote:

> If memory serves me right, Michael Zatopek wrote:
>> I've done my best to verify that there are no network related issues.
>> Does anybody else have the most recent subversion + apache22 +
>> Freebsd 8.0 running? I kinda feel like there's some sort of version
>> incompatibility happening.
>> Is there any way to get more detailed error logs out of subversion or
>> apache in this case? I've got apache's logging turned up all the way
>> and it only gives the 4 vague messages from my original description.
>> At what point should I move this over onto the dev mailing list?
> Hi Michael--
> I don't have any FreeBSD 8.0 Subversion servers (though I can report
> excellent experiences with FreeBSD 6.4 and 7.3 as servers), however...
> At what point did you build and install these ports? There was a
> little
> bit of shuffling around about two weeks back when the various FreeBSD
> ports that use APR (Apache HTTPD and Subversion are two of these) were
> all converted to use APR from the ports tree, rather then potentially
> using bundled versions. I vaguely recall this taking a little time to
> get sorted out, but if you built ports in the middle of this it might
> have gotten things in an odd state. Note that there is no particular
> evidence pointing in this direction, but it just came to mind. If
> this
> is true, maybe try updating everything with portupgrade,
> portmaster, or
> some other similar tool (remember to check UPDATING first)?
> Not sure how applicable this would be, but does svn+ssh:// access
> work?
> Bruce.


Yeah, I've been running these two repositories on a FreeBSD 6.4
system for several years with the same configuration with no
troubles. I did the initial install about 2 weeks ago. I have been
rebuilding every time the ports tree for anything I'm running gets
updated hoping that will fix it (most recently this morning) with no
luck. I did try switching to Apache 2.0 instead of 2.2 a few days ago
and that failed to build (probably because of the APR stuff
happening). I might try that again since I think Subversion got an
APR related update in ports since then but I probably won't get to it
till Monday.

I haven't tried svn+ssh yet either, but since it will checkout via
http on the local machine, and is navigable via firefox, it didn't
seem to be an issue with the repository itself that svn+ssh might
rule out. I might give that a try Monday as well.

Thanks for the suggestions. I'll give both a shot just to rule them
out or turn up more info early next week and let you know what happens.

Received on 2010-06-04 22:55:09 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.