You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Matt <ma...@channeladvisor.com> on 2009/09/01 20:25:41 UTC

Apache Error after upgrading from 1.4.3 to 1.5.7

Hi,

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.

So, any help to push me in the right direction would be appreciated.

Thanks,

M

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2389924

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

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

Posted by Matt <ma...@channeladvisor.com>.
Ah, cool.  Thanks, I see now.  I noticed another problem, I was using the wrong parameters to configure the build.  It should be --with-apr= and --with-apr-util=

I don't know why I didn't think of this earlier but what I did was point the latest install 1.6.5 to the apr and apr-util within my working 1.4.3 install.  That fixed my problem and its working now.

Thanks a lot guys.  

Matt

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390772

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: Apache Error after upgrading from 1.4.3 to 1.5.7

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Sep 3, 2009, at 08:18, Matt wrote:
> Chris wrote:
>> On Wed, Sep 2, 2009 at 2:15 PM, Matt wrote:
>>> Is there a way to see what version of apr apache is running?
>>
>> I would suggest something along the lines of this:
>>
>> cshelton@batboy ~ $ ldd /usr/sbin/apache2
>>        linux-gate.so.1 =>  (0xffffe000)
>>        libm.so.6 => /lib/tls/libm.so.6 (0xb7f0c000)
>>        libpcre.so.0 => /usr/lib/libpcre.so.0 (0xb7edc000)
>>        libz.so.1 => /lib/libz.so.1 (0xb7eca000)
>>        libbz2.so.1 => /lib/libbz2.so.1 (0xb7eb9000)
>>        libaprutil-1.so.0 => /usr/lib/libaprutil-1.so.0 (0xb7e9a000)
>>        libdb-4.5.so => /usr/lib/libdb-4.5.so (0xb7d88000)
>>        libgdbm.so.3 => /usr/lib/libgdbm.so.3 (0xb7d82000)
>>        libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb7d64000)
>>        libapr-1.so.0 => /usr/lib/libapr-1.so.0 (0xb7d3e000)
>>        libuuid.so.1 => /lib/libuuid.so.1 (0xb7d39000)
>>        librt.so.1 => /lib/tls/librt.so.1 (0xb7d2f000)
>>        libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7d01000)
>>        libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb7ceb000)
>>        libdl.so.2 => /lib/libdl.so.2 (0xb7ce7000)
>>        libc.so.6 => /lib/tls/libc.so.6 (0xb7bc6000)
>>        /lib/ld-linux.so.2 (0xb7f3d000)
>>
>> Then:
>>
>> cshelton@batboy ~ $ file /usr/lib/libaprutil-1.so.0
>> /usr/lib/libaprutil-1.so.0: symbolic link to `libaprutil-1.so.0.3.9'
>>
>> cshelton@batboy ~ $ file /usr/lib/libapr-1.so.0
>> /usr/lib/libapr-1.so.0: symbolic link to `libapr-1.so.0.3.8'
>>
>> My system is running apr-util version 1.3.9 and apr version 1.3.8.
>> The apache httpd is a recent 2.2 version.
>
> Huh?  I'm not sure I'm following you.  Is this just a way to trick  
> my system into using the latest version?  I'm running apache 2.0  
> though.

You asked "Is there a way to see what version of apr apache is  
running?" The answer is to use the "ldd" program, giving it the path  
to your Apache program. Chris was showing you the output from his  
system, which shows his apache2 linking with libapr-1.so.0 and  
libaprutil-1.so.0. He then further revealed, using the "file" command  
on those libraries, that they are actually symbolic links, and that  
the names of the files they point to contain the version numbers of  
apr and apr-util. He was suggesting you run similar commands on your  
system to find out what versions of apr and apr-util your Apache is  
using.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390651

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

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

Posted by Matt <ma...@channeladvisor.com>.
> Matt,
> 
> On Wed, Sep 2, 2009 at 2:15 PM, Matt<ma...@channeladvisor.com> wrote:
> > 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?
> 
> I would suggest something along the lines of this:
> 
> cshelton@batboy ~ $ ldd /usr/sbin/apache2
>         linux-gate.so.1 =>  (0xffffe000)
>         libm.so.6 => /lib/tls/libm.so.6 (0xb7f0c000)
>         libpcre.so.0 => /usr/lib/libpcre.so.0 (0xb7edc000)
>         libz.so.1 => /lib/libz.so.1 (0xb7eca000)
>         libbz2.so.1 => /lib/libbz2.so.1 (0xb7eb9000)
>         libaprutil-1.so.0 => /usr/lib/libaprutil-1.so.0 (0xb7e9a000)
>         libdb-4.5.so => /usr/lib/libdb-4.5.so (0xb7d88000)
>         libgdbm.so.3 => /usr/lib/libgdbm.so.3 (0xb7d82000)
>         libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb7d64000)
>         libapr-1.so.0 => /usr/lib/libapr-1.so.0 (0xb7d3e000)
>         libuuid.so.1 => /lib/libuuid.so.1 (0xb7d39000)
>         librt.so.1 => /lib/tls/librt.so.1 (0xb7d2f000)
>         libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7d01000)
>         libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb7ceb000)
>         libdl.so.2 => /lib/libdl.so.2 (0xb7ce7000)
>         libc.so.6 => /lib/tls/libc.so.6 (0xb7bc6000)
>         /lib/ld-linux.so.2 (0xb7f3d000)
> 
> Then:
> 
> cshelton@batboy ~ $ file /usr/lib/libaprutil-1.so.0
> /usr/lib/libaprutil-1.so.0: symbolic link to `libaprutil-1.so.0.3.9'
> 
> cshelton@batboy ~ $ file /usr/lib/libapr-1.so.0
> /usr/lib/libapr-1.so.0: symbolic link to `libapr-1.so.0.3.8'
> 
> My system is running apr-util version 1.3.9 and apr version 1.3.8.
> The apache httpd is a recent 2.2 version.
> 
> chris

Huh?  I'm not sure I'm following you.  Is this just a way to trick my system into using the latest version?  I'm running apache 2.0 though.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390644

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].


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

Posted by Chris Shelton <cs...@shelton-family.net>.
Matt,

On Wed, Sep 2, 2009 at 2:15 PM, Matt<ma...@channeladvisor.com> wrote:
> 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?

I would suggest something along the lines of this:

cshelton@batboy ~ $ ldd /usr/sbin/apache2
        linux-gate.so.1 =>  (0xffffe000)
        libm.so.6 => /lib/tls/libm.so.6 (0xb7f0c000)
        libpcre.so.0 => /usr/lib/libpcre.so.0 (0xb7edc000)
        libz.so.1 => /lib/libz.so.1 (0xb7eca000)
        libbz2.so.1 => /lib/libbz2.so.1 (0xb7eb9000)
        libaprutil-1.so.0 => /usr/lib/libaprutil-1.so.0 (0xb7e9a000)
        libdb-4.5.so => /usr/lib/libdb-4.5.so (0xb7d88000)
        libgdbm.so.3 => /usr/lib/libgdbm.so.3 (0xb7d82000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb7d64000)
        libapr-1.so.0 => /usr/lib/libapr-1.so.0 (0xb7d3e000)
        libuuid.so.1 => /lib/libuuid.so.1 (0xb7d39000)
        librt.so.1 => /lib/tls/librt.so.1 (0xb7d2f000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7d01000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb7ceb000)
        libdl.so.2 => /lib/libdl.so.2 (0xb7ce7000)
        libc.so.6 => /lib/tls/libc.so.6 (0xb7bc6000)
        /lib/ld-linux.so.2 (0xb7f3d000)

Then:

cshelton@batboy ~ $ file /usr/lib/libaprutil-1.so.0
/usr/lib/libaprutil-1.so.0: symbolic link to `libaprutil-1.so.0.3.9'

cshelton@batboy ~ $ file /usr/lib/libapr-1.so.0
/usr/lib/libapr-1.so.0: symbolic link to `libapr-1.so.0.3.8'

My system is running apr-util version 1.3.9 and apr version 1.3.8.
The apache httpd is a recent 2.2 version.

chris

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390420

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].


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

Posted by Matt <ma...@channeladvisor.com>.
> 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?

Thanks,

Matt

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390383

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: Apache Error after upgrading from 1.4.3 to 1.5.7

Posted by Ryan Schmidt <su...@ryandesign.com>.
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.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390203

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

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

Posted by Matt <ma...@channeladvisor.com>.
> On Sep 1, 2009, at 15: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.

Thanks,

Matt

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390193

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: Apache Error after upgrading from 1.4.3 to 1.5.7

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Sep 1, 2009, at 15: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.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390164

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: Apache Error after upgrading from 1.4.3 to 1.5.7

Posted by Radomir Zoltowski <ra...@s3group.com>.
Matt wrote:
> Hi,
>
> 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.
>
> So, any help to push me in the right direction would be appreciated.
>
> Thanks,
>
> M
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2389924
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
>   
It's a long shot, but first try to disable

LoadModule dav_svn_module     modules/mod_dav_svn.so
LoadModule authz_svn_module   modules/mod_authz_svn.so

and restart Apache. If it works, replace modules with new ones.

The information contained in this e-mail and in any attachments is confidential and is designated solely for the attention of the intended recipient(s). If you are not an intended recipient, you must not use, disclose, copy, distribute or retain this e-mail or any part thereof. If you have received this e-mail in error, please notify the sender by return e-mail and delete all copies of this e-mail from your computer system(s).
Please direct any additional queries to: communications@s3group.com.
Thank You.
Silicon and Software Systems Limited. Registered in Ireland no. 378073.
Registered Office: South County Business Park, Leopardstown, Dublin 18

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390116

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].