You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by ji...@accenture.com on 2013/02/05 13:29:49 UTC
[mp2] mod_perl resulting apache failure
-------------8<---------- Start Bug Report ------------8<----------
1. Problem Description:
Apache start is failing after adding mod_perl module in httpd.conf.
2. Used Components and their Configuration:
*** mod_perl version 2.000007
*** using /home/soni498/mod_perl-2.0.7/lib/Apache2/BuildConfig.pm
*** Makefile.PL options:
MP_APR_LIB => aprext
MP_APXS => /usr/apache02/httpd_2.2.20/bin/apxs
MP_COMPAT_1X => 1
MP_GENERATE_XS => 1
MP_LIBNAME => mod_perl
MP_USE_DSO => 1
*** /usr/httpd2.2.20/httpd/bin/httpd -V
Server version: Apache/2.2.20 (Unix)
Server built: Feb 5 2013 08:10:24
Server's Module Magic Number: 20051115:28
Server loaded: APR 1.4.5, APR-Util 1.3.12
Compiled using: APR 1.4.5, APR-Util 1.3.12
Architecture: 32-bit
Server MPM: Prefork
threaded: no
forked: yes (variable process count)
Server compiled with....
-D APACHE_MPM_DIR="server/mpm/prefork"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_PROC_PTHREAD_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=128
-D HTTPD_ROOT="/usr/httpd2.2.20/httpd"
-D SUEXEC_BIN="/usr/httpd2.2.20/httpd/bin/suexec"
-D DEFAULT_PIDLOG="logs/httpd.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_LOCKFILE="logs/accept.lock"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="conf/mime.types"
-D SERVER_CONFIG_FILE="conf/httpd.conf"
*** /usr/bin/ldd /usr/httpd2.2.20/httpd/bin/httpd
libm.so.2 => /lib/libm.so.2
libaprutil-1.so.0 => /usr/httpd2.2.20/httpd/lib/libaprutil-1.so.0
libexpat.so.0 => /usr/httpd2.2.20/httpd/lib/libexpat.so.0
libiconv.so.2 => /usr/local/lib/libiconv.so.2
libapr-1.so.0 => /usr/httpd2.2.20/httpd/lib/libapr-1.so.0
libuuid.so.1 => /lib/libuuid.so.1
libsendfile.so.1 => /lib/libsendfile.so.1
librt.so.1 => /lib/librt.so.1
libsocket.so.1 => /lib/libsocket.so.1
libnsl.so.1 => /lib/libnsl.so.1
libpthread.so.1 => /lib/libpthread.so.1
libc.so.1 => /lib/libc.so.1
libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1
libaio.so.1 => /lib/libaio.so.1
libmd.so.1 => /lib/libmd.so.1
libmp.so.2 => /lib/libmp.so.2
libscf.so.1 => /lib/libscf.so.1
libdoor.so.1 => /lib/libdoor.so.1
libuutil.so.1 => /lib/libuutil.so.1
libgen.so.1 => /lib/libgen.so.1
/lib/libm/libm_hwcap1.so.2
/platform/SUNW,SPARC-Enterprise/lib/libc_psr.so.1
*** (apr|apu)-config linking info
-L/usr/apache02/httpd_2.2.20/lib -laprutil-1 -lexpat -liconv
-L/usr/apache02/httpd_2.2.20/lib -lapr-1 -luuid -lsendfile -lrt -lsocket -lnsl -lpthread
*** /usr/local/bin/perl -V
Summary of my perl5 (revision 5 version 14 subversion 2) configuration:
Platform:
osname=solaris, osvers=2.10, archname=sun4-solaris-thread-multi
uname='sunos sz1061 5.10 generic_147440-19 sun4u sparc sunw,sparc-enterprise '
config_args='-de -Dcc=gcc'
hint=previous, useposix=true, d_sigaction=define
useithreads=define, usemultiplicity=define
useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef
use64bitint=undef, use64bitall=undef, uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc='gcc', ccflags ='-D_REENTRANT -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV -DPERL_USE_SAFE_PUTENV',
optimize='-O',
cppflags='-D_REENTRANT -fno-strict-aliasing -pipe -I/usr/local/include -D_REENTRANT -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV'
ccversion='', gccversion='3.4.6', gccosandvers='solaris2.10'
intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=4321
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
alignbytes=8, prototype=define
Linker and Libraries:
ld='gcc', ldflags =' -L/usr/local/lib '
libpth=/usr/local/lib /usr/lib /usr/ccs/lib
libs=-lsocket -lnsl -ldl -lm -lpthread -lc
perllibs=-lsocket -lnsl -ldl -lm -lpthread -lc
libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
gnulibc_version=''
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
cccdlflags='-fPIC', lddlflags='-G -L/usr/local/lib'
Characteristics of this binary (from libperl):
Compile-time options: MULTIPLICITY PERL_DONT_CREATE_GVSV
PERL_IMPLICIT_CONTEXT PERL_MALLOC_WRAP
PERL_PRESERVE_IVUV PERL_USE_SAFE_PUTENV USE_ITHREADS
USE_LARGE_FILES USE_PERLIO USE_PERL_ATOF
USE_REENTRANT_API
Built under solaris
Compiled at Feb 5 2013 10:37:08
%ENV:
PERL_LWP_USE_HTTP_10="1"
@INC:
/usr/local/lib/perl5/site_perl/5.14.2/sun4-solaris-thread-multi
/usr/local/lib/perl5/site_perl/5.14.2
/usr/local/lib/perl5/5.14.2/sun4-solaris-thread-multi
/usr/local/lib/perl5/5.14.2
.
*** Packages of interest status:
Apache2 : -
Apache2::Request : -
CGI : 3.52
ExtUtils::MakeMaker: 6.57_05
LWP : -
mod_perl : -
mod_perl2 : 2.000007
3. This is the core dump trace: (if you get a core dump):
[CORE TRACE COMES HERE]
This report was generated by t/REPORT on Tue Feb 5 12:22:54 2013 GMT.
-------------8<---------- End Bug Report --------------8<----------
Note: Complete the rest of the details and post this bug report to
modperl <at> perl.apache.org. To subscribe to the list send an empty
email to modperl-subscribe@perl.apache.org.
[root@sz1061 mod_perl-2.0.7]#
Thanks & Regards,
-----------------------------------------------------
Jitendra Soni
Accenture, Bangalore INDIA
Mailto: jitendra.soni@accenture.com<ma...@accenture.com>
Phone: (+91) 99860 29897
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited.
Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________
www.accenture.com
Re: [mp2] mod_perl resulting apache failure
Posted by Jie Gao <J....@sydney.edu.au>.
Looks like mixing of different installations.
To ensure a clean separation of Solaris' installations from yours,
compile perl, apache, mod_perl and other required packages, and install
them in /usr/local. I'd use the "-L" and "-R" flags to lock the paths to
/usr/local/lib and other local lib locations, something that has worked
for me for many years.
Regards,
Jie
* jitendra.soni@accenture.com <ji...@accenture.com> wrote:
> Date: Tue, 5 Feb 2013 12:29:49 +0000
> From: jitendra.soni@accenture.com
> To: modperl@perl.apache.org
> Subject: [mp2] mod_perl resulting apache failure
>
> -------------8<---------- Start Bug Report ------------8<----------
> 1. Problem Description:
>
> Apache start is failing after adding mod_perl module in httpd.conf.
>
> 2. Used Components and their Configuration:
>
> *** mod_perl version 2.000007
>
> *** using /home/soni498/mod_perl-2.0.7/lib/Apache2/BuildConfig.pm
>
> *** Makefile.PL options:
> MP_APR_LIB => aprext
> MP_APXS => /usr/apache02/httpd_2.2.20/bin/apxs
> MP_COMPAT_1X => 1
> MP_GENERATE_XS => 1
> MP_LIBNAME => mod_perl
> MP_USE_DSO => 1
>
>
> *** /usr/httpd2.2.20/httpd/bin/httpd -V
> Server version: Apache/2.2.20 (Unix)
> Server built: Feb 5 2013 08:10:24
> Server's Module Magic Number: 20051115:28
> Server loaded: APR 1.4.5, APR-Util 1.3.12
> Compiled using: APR 1.4.5, APR-Util 1.3.12
> Architecture: 32-bit
> Server MPM: Prefork
> threaded: no
> forked: yes (variable process count)
> Server compiled with....
> -D APACHE_MPM_DIR="server/mpm/prefork"
> -D APR_HAS_SENDFILE
> -D APR_HAS_MMAP
> -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
> -D APR_USE_PROC_PTHREAD_SERIALIZE
> -D APR_USE_PTHREAD_SERIALIZE
> -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
> -D APR_HAS_OTHER_CHILD
> -D AP_HAVE_RELIABLE_PIPED_LOGS
> -D DYNAMIC_MODULE_LIMIT=128
> -D HTTPD_ROOT="/usr/httpd2.2.20/httpd"
> -D SUEXEC_BIN="/usr/httpd2.2.20/httpd/bin/suexec"
> -D DEFAULT_PIDLOG="logs/httpd.pid"
> -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
> -D DEFAULT_LOCKFILE="logs/accept.lock"
> -D DEFAULT_ERRORLOG="logs/error_log"
> -D AP_TYPES_CONFIG_FILE="conf/mime.types"
> -D SERVER_CONFIG_FILE="conf/httpd.conf"
>
> *** /usr/bin/ldd /usr/httpd2.2.20/httpd/bin/httpd
> libm.so.2 => /lib/libm.so.2
> libaprutil-1.so.0 => /usr/httpd2.2.20/httpd/lib/libaprutil-1.so.0
> libexpat.so.0 => /usr/httpd2.2.20/httpd/lib/libexpat.so.0
> libiconv.so.2 => /usr/local/lib/libiconv.so.2
> libapr-1.so.0 => /usr/httpd2.2.20/httpd/lib/libapr-1.so.0
> libuuid.so.1 => /lib/libuuid.so.1
> libsendfile.so.1 => /lib/libsendfile.so.1
> librt.so.1 => /lib/librt.so.1
> libsocket.so.1 => /lib/libsocket.so.1
> libnsl.so.1 => /lib/libnsl.so.1
> libpthread.so.1 => /lib/libpthread.so.1
> libc.so.1 => /lib/libc.so.1
> libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1
> libaio.so.1 => /lib/libaio.so.1
> libmd.so.1 => /lib/libmd.so.1
> libmp.so.2 => /lib/libmp.so.2
> libscf.so.1 => /lib/libscf.so.1
> libdoor.so.1 => /lib/libdoor.so.1
> libuutil.so.1 => /lib/libuutil.so.1
> libgen.so.1 => /lib/libgen.so.1
> /lib/libm/libm_hwcap1.so.2
> /platform/SUNW,SPARC-Enterprise/lib/libc_psr.so.1
>
>
> *** (apr|apu)-config linking info
>
> -L/usr/apache02/httpd_2.2.20/lib -laprutil-1 -lexpat -liconv
> -L/usr/apache02/httpd_2.2.20/lib -lapr-1 -luuid -lsendfile -lrt -lsocket -lnsl -lpthread
>
>
>
> *** /usr/local/bin/perl -V
> Summary of my perl5 (revision 5 version 14 subversion 2) configuration:
>
> Platform:
> osname=solaris, osvers=2.10, archname=sun4-solaris-thread-multi
> uname='sunos sz1061 5.10 generic_147440-19 sun4u sparc sunw,sparc-enterprise '
> config_args='-de -Dcc=gcc'
> hint=previous, useposix=true, d_sigaction=define
> useithreads=define, usemultiplicity=define
> useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef
> use64bitint=undef, use64bitall=undef, uselongdouble=undef
> usemymalloc=n, bincompat5005=undef
> Compiler:
> cc='gcc', ccflags ='-D_REENTRANT -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV -DPERL_USE_SAFE_PUTENV',
> optimize='-O',
> cppflags='-D_REENTRANT -fno-strict-aliasing -pipe -I/usr/local/include -D_REENTRANT -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV'
> ccversion='', gccversion='3.4.6', gccosandvers='solaris2.10'
> intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=4321
> d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
> ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
> alignbytes=8, prototype=define
> Linker and Libraries:
> ld='gcc', ldflags =' -L/usr/local/lib '
> libpth=/usr/local/lib /usr/lib /usr/ccs/lib
> libs=-lsocket -lnsl -ldl -lm -lpthread -lc
> perllibs=-lsocket -lnsl -ldl -lm -lpthread -lc
> libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
> gnulibc_version=''
> Dynamic Linking:
> dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
> cccdlflags='-fPIC', lddlflags='-G -L/usr/local/lib'
>
>
> Characteristics of this binary (from libperl):
> Compile-time options: MULTIPLICITY PERL_DONT_CREATE_GVSV
> PERL_IMPLICIT_CONTEXT PERL_MALLOC_WRAP
> PERL_PRESERVE_IVUV PERL_USE_SAFE_PUTENV USE_ITHREADS
> USE_LARGE_FILES USE_PERLIO USE_PERL_ATOF
> USE_REENTRANT_API
> Built under solaris
> Compiled at Feb 5 2013 10:37:08
> %ENV:
> PERL_LWP_USE_HTTP_10="1"
> @INC:
> /usr/local/lib/perl5/site_perl/5.14.2/sun4-solaris-thread-multi
> /usr/local/lib/perl5/site_perl/5.14.2
> /usr/local/lib/perl5/5.14.2/sun4-solaris-thread-multi
> /usr/local/lib/perl5/5.14.2
> .
>
> *** Packages of interest status:
>
> Apache2 : -
> Apache2::Request : -
> CGI : 3.52
> ExtUtils::MakeMaker: 6.57_05
> LWP : -
> mod_perl : -
> mod_perl2 : 2.000007
>
>
> 3. This is the core dump trace: (if you get a core dump):
>
> [CORE TRACE COMES HERE]
>
> This report was generated by t/REPORT on Tue Feb 5 12:22:54 2013 GMT.
>
> -------------8<---------- End Bug Report --------------8<----------
>
> Note: Complete the rest of the details and post this bug report to
> modperl <at> perl.apache.org. To subscribe to the list send an empty
> email to modperl-subscribe@perl.apache.org.
>
>
> [root@sz1061 mod_perl-2.0.7]#
>
> Thanks & Regards,
> -----------------------------------------------------
> Jitendra Soni
> Accenture, Bangalore INDIA
> Mailto: jitendra.soni@accenture.com<ma...@accenture.com>
> Phone: (+91) 99860 29897
>
>
> ________________________________
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited.
>
> Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
>
> ______________________________________________________________________________________
>
> www.accenture.com
RE: [mp2] mod_perl resulting apache failure
Posted by ji...@accenture.com.
Thank you so muchhhhh Torsten its working for me.
Party due for you.
Thanks once again.
Regards,
Jitendra
-----Original Message-----
From: Torsten Förtsch [mailto:torsten.foertsch@gmx.net]
Sent: Tuesday, February 05, 2013 8:42 PM
To: Soni, Jitendra
Cc: modperl@perl.apache.org
Subject: Re: [mp2] mod_perl resulting apache failure
On 02/05/2013 03:37 PM, jitendra.soni@accenture.com wrote:
> Also, can you please elaborate how 32bits arcitecture can create issue here.
Did you read the thread I mentioned? In particular:
http://www.gossamer-threads.com/lists/modperl/modperl/103551#103551
I just noticed that the link to the patch at the end of the thread is currently not available. It seems this one does the same:
http://jkaluza.fedorapeople.org/mod_perl/mod_perl-2.0.5-nolfs.patch
Torsten
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited.
Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________
www.accenture.com
Re: [mp2] mod_perl resulting apache failure
Posted by Torsten Förtsch <to...@gmx.net>.
On 02/05/2013 03:37 PM, jitendra.soni@accenture.com wrote:
> Also, can you please elaborate how 32bits arcitecture can create issue here.
Did you read the thread I mentioned? In particular:
http://www.gossamer-threads.com/lists/modperl/modperl/103551#103551
I just noticed that the link to the patch at the end of the thread is
currently not available. It seems this one does the same:
http://jkaluza.fedorapeople.org/mod_perl/mod_perl-2.0.5-nolfs.patch
Torsten
RE: [mp2] mod_perl resulting apache failure
Posted by ji...@accenture.com.
Hi Torsten,
I ran make test and it failed with below errors. Also, can you please elaborate how 32bits arcitecture can create issue here.
[soni498@sz1061:NODB mod_perl-2.0.7]$ make test
cd "src/modules/perl" && make
/usr/bin/perl -Iblib/arch -Iblib/lib \
t/TEST -clean
[warning] Skipping 'set unlimited ulimit for coredumps', since we are running as a non-root user on Solaris
APACHE_TEST_GROUP= APACHE_TEST_HTTPD= APACHE_TEST_PORT= APACHE_TEST_USER= APACHE_TEST_APXS= \
/usr/bin/perl -Iblib/arch -Iblib/lib \
t/TEST -bugreport -verbose=0
[warning] Skipping 'set unlimited ulimit for coredumps', since we are running as a non-root user on Solaris
/usr/httpd2.2.20/httpd/bin/httpd -d /home/soni498/mod_perl-2.0.7/t -f /home/soni498/mod_perl-2.0.7/t/conf/httpd.conf -D APACHE2 -D PERL_USEITHREADS
using Apache/2.2.20 (prefork MPM)
waiting 300 seconds for server to start: ..............................................................................................................................................................................................................................................................................................................
waiting 300 seconds for server to start: not ok
[ error] giving up after 301 secs. If you think that your system
is slow or overloaded try again with a longer timeout value.
by setting the environment variable APACHE_TEST_STARTUP_TIMEOUT
to a high value (e.g. 600) and repeat the last command.
[ error] server failed to start! (t/logs/error_log wasn't created, start the server in the debug mode)
+--------------------------------------------------------+
| Please file a bug report: http://perl.apache.org/bugs/ |
+--------------------------------------------------------+
*** Error code 1
make: Fatal error: Command failed for target `run_tests'
[soni498@sz1061:NODB mod_perl-2.0.7]$ cd
Thanks & Regards,
-----------------------------------------------------
Jitendra Soni
Accenture, Bangalore INDIA
Mailto: jitendra.soni@accenture.com
Phone: (+91) 99860 29897
-----Original Message-----
From: Torsten Förtsch [mailto:torsten.foertsch@gmx.net]
Sent: Tuesday, February 05, 2013 6:59 PM
To: Soni, Jitendra
Cc: modperl@perl.apache.org
Subject: Re: [mp2] mod_perl resulting apache failure
On 02/05/2013 01:29 PM, jitendra.soni@accenture.com wrote:
> 1. Problem Description:
>
> Apache start is failing after adding mod_perl module in httpd.conf.
>
I take it you ran "make test" and all tests passed? Then make sure you use the same perl/modperl/httpd combination. Make sure all the paths are correct.
On a linux box the best way to do that is to look at /proc/$HTTPD_PID/maps when the modperl test suite is running. Then start your production server without modperl, take the output and compare it with the modperl case.
Then you can setup your production server to produce core dumps (ulimit, CoreDumpDirectory). Inspect the core dump with GDB. It lists all shared libraries it loads. It also can generate a stack trace that can help identifying your problem.
These recommendations are not very useful in pointing directly to your problem. But given the little information you provide this is all I can do.
The only thing I see is that you are using 32 bit architecture. There is a large-file-support related problem there. See:
http://www.gossamer-threads.com/lists/modperl/modperl/103514#103514
The patch mentioned at the end of the thread may help. But if that were the case "make test" should have failed.
I don't have any 32 bit system here and I don't fully understand the implications of the patch.
Torsten
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited.
Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________
www.accenture.com
Re: [mp2] mod_perl resulting apache failure
Posted by Torsten Förtsch <to...@gmx.net>.
On 02/05/2013 01:29 PM, jitendra.soni@accenture.com wrote:
> 1. Problem Description:
>
> Apache start is failing after adding mod_perl module in httpd.conf.
>
I take it you ran "make test" and all tests passed? Then make sure you
use the same perl/modperl/httpd combination. Make sure all the paths are
correct.
On a linux box the best way to do that is to look at
/proc/$HTTPD_PID/maps when the modperl test suite is running. Then start
your production server without modperl, take the output and compare it
with the modperl case.
Then you can setup your production server to produce core dumps (ulimit,
CoreDumpDirectory). Inspect the core dump with GDB. It lists all shared
libraries it loads. It also can generate a stack trace that can help
identifying your problem.
These recommendations are not very useful in pointing directly to your
problem. But given the little information you provide this is all I can do.
The only thing I see is that you are using 32 bit architecture. There is
a large-file-support related problem there. See:
http://www.gossamer-threads.com/lists/modperl/modperl/103514#103514
The patch mentioned at the end of the thread may help. But if that were
the case "make test" should have failed.
I don't have any 32 bit system here and I don't fully understand the
implications of the patch.
Torsten