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

RE: Re: Apache Error after upgrading from 1.4.3 to 1.5.7

From: Matt <mattr_at_channeladvisor.com>
Date: Wed, 2 Sep 2009 11:15:19 -0700 (PDT)

> On Sep 2, 2009, at 08:25, Matt wrote:
> >>> When I upgraded to 1.5.7 my existing apache server fails with the
> >>> following when you try and access the existing repository. (This
> >>> is showing up in my httpd error_log.) I don't get anything in the
> >>> svn log.
> >>>
> >>> [Tue Sep 01 16:19:45 2009] [notice] child pid 3356 exit signal
> >>> Segmentation fault (11)
> >>>
> >>> If I go back and build 1.4.3 then things start working again. I'm
> >>> using the default make install running on CentOS release 4.4.
> >>> Running Apache version 2.0.52 too.
> >>
> >> Was your new Subversion 1.5.7 built against the same version of apr
> >> and apr-util as your Apache 2.0.52? It needs to be.
> >
> > Umm, thats a good question. Is there a way I can look at the
> > orginal 1.4.3 install and see what it it was built against? I
> > originally didn't build out this server, so I assume the new version
> > is getting built against whatever is in the deps distribution.
> If you want to use mod_dav_svn with Apache 2.0.x, mod_dav_svn must be
> built with apr and apr-util 0.9.x. (For Apache 2.2.x, it must be apr
> and apr-util 1.x.) subversion-deps-1.5.7.tar.gz contains apr 1.3.5 and
> apr-util 1.3.7, so that would not be compatible with Apache 2.0.x.
> There are already copies of apr and apr-util 0.9.x installed on your
> system, either as part of Apache 2.0.x or installed separately and
> your Apache 2.0.x is using it. Point Subversion's configure script at
> that apr and apr-util using the --with-apr-config and --with-apu-
> config options and it should work.

So, I'm confused. I went back and tried pointing apr-config and apu-config with all the instances I found on my machine, such as:

./configure --with-apr-config=/usr/bin/apr-config --with-apu-config=/usr/bin/apu-config

In every case I got the same results. Even if I remove the svn modules from the httpd.config apache throws the same exception. Going back in building svn 1.4.3 and it works. Is there a way to see what version of apr apache is running?




To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-02 20:16:15 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.