You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Bennett Haselton <be...@peacefire.org> on 2006/02/02 02:08:13 UTC
errors in module.t & others when installing mod_perl
Now I'm trying to install mod_perl 2.0.2 on a different machine running
Apache/2.0.49. When I run "make test", this is the chart of errors that I
get at the end:
Failed Test Stat Wstat Total Fail Failed List of Failed
------------------------------------------------------------------------------
t/api/module.t 317 11 3.47% 15 20 25 30 35
40
45 50 55 60 65
t/hooks/hookrun.t 255 65280 10 18 180.00% 2-10
t/hooks/stacked_handlers2.t 255 65280 1 2 200.00% 1
t/user/rewrite.t 255 65280 ?? ?? % ??
(Incidentally, I ran "make test" a second time to see if the results were a
fluke, and I got th exact same results. And it can't be a coincidence that
the 11 tests that filed in the first suite were all evenly divisible by 5;
don't know if that points to a likely cause?)
Any ideas on what I can do to get it to install?
Following the instructions at
http://perl.apache.org/docs/2.0/user/help/help.html#_C_make_test___Failures
I also ran:
make test TEST_VERBOSE=1 TEST_FILES="t/api/module.t t/hooks/hookrun.t
t/hooks/stacked_handlers2.t t/user/rewrite.t"
and I am pasting the results of the resulting t/logs/error_log file
(everything between the ">>>>>" lines):
>>>>>
[Wed Feb 01 16:49:19 2006] [debug] util_ldap.c(1129): LDAP cache: Unable to
init Shared Cache: no file
[Wed Feb 01 16:49:19 2006] [notice] LDAP: Built with OpenLDAP LDAP SDK
[Wed Feb 01 16:49:19 2006] [notice] LDAP: SSL support unavailable
[Wed Feb 01 16:49:19 2006] [notice] suEXEC mechanism enabled (wrapper:
/usr/sbin/suexec)
[Wed Feb 01 16:49:19 2006] [info] Init: Initializing OpenSSL library
[Wed Feb 01 16:49:19 2006] [info] Init: Seeding PRNG with 0 bytes of
entropy
[Wed Feb 01 16:49:19 2006] [info] Init: Generating temporary RSA private
keys (512/1024 bits)
[Wed Feb 01 16:49:19 2006] [info] Init: Generating temporary DH parameters
(512/1024 bits)
[Wed Feb 01 16:49:19 2006] [warn] Init: Session Cache is not configured
[hint: SSLSessionCache]
[Wed Feb 01 16:49:19 2006] [info] Init: Initializing (virtual) servers for
SSL
[Wed Feb 01 16:49:19 2006] [info] Server: Apache/2.0.49, Interface:
mod_ssl/2.0.49, Library: OpenSSL/0.9.7a
END in modperl_extra.pl, pid=23644
[Wed Feb 01 16:49:21 2006] [notice] Digest: generating secret for digest
authentication ...
[Wed Feb 01 16:49:21 2006] [notice] Digest: done
[Wed Feb 01 16:49:21 2006] [debug] util_ldap.c(1129): LDAP cache: Unable to
init Shared Cache: no file
[Wed Feb 01 16:49:21 2006] [notice] LDAP: Built with OpenLDAP LDAP SDK
[Wed Feb 01 16:49:21 2006] [notice] LDAP: SSL support unavailable
[Wed Feb 01 16:49:22 2006] [info] Init: Initializing OpenSSL library
[Wed Feb 01 16:49:22 2006] [info] Init: Seeding PRNG with 0 bytes of
entropy
[Wed Feb 01 16:49:22 2006] [info] Init: Generating temporary RSA private
keys (512/1024 bits)
[Wed Feb 01 16:49:22 2006] [info] Init: Generating temporary DH parameters
(512/1024 bits)
[Wed Feb 01 16:49:22 2006] [info] Init: Initializing (virtual) servers for
SSL
[Wed Feb 01 16:49:22 2006] [info] Server: Apache/2.0.49, Interface:
mod_ssl/2.0.49, Library: OpenSSL/0.9.7a
[Wed Feb 01 16:49:22 2006] [error] (13)Permission denied: Can't clean stale
key files from directory "/usr/local/frontpage/version5.0/apache-fp" in
FrontPageCleanup().
[Wed Feb 01 16:49:22 2006] [error] Not running as root in
FrontPageCheckup(). Until this problem is fixed, the FrontPage security
patch is disabled and the FrontPage extensions may not work correctly.
[Wed Feb 01 16:49:22 2006] [notice] Apache/2.0.49 (Fedora) world domination
series/2.0 DAV/2 mod_webapp/1.2.0-dev PHP/4.3.4 mod_ssl/2.0.49
OpenSSL/0.9.7a mod_perl/2.0.2 Perl/v5.8.3 configured -- resuming normal
operations
[Wed Feb 01 16:49:22 2006] [info] Server built: May 6 2004 07:15:13
[Wed Feb 01 16:49:22 2006] [debug] prefork.c(955): AcceptMutex: sysvsem
(default: sysvsem)
# Failed test 15 in
/tmp/modperl2test/mod_perl-2.0.2/t/response/TestAPI/module.pm at line 88
# Failed test 20 in
/tmp/modperl2test/mod_perl-2.0.2/t/response/TestAPI/module.pm at line 88
fail #2
# Failed test 25 in
/tmp/modperl2test/mod_perl-2.0.2/t/response/TestAPI/module.pm at line 88
fail #3
# Failed test 30 in
/tmp/modperl2test/mod_perl-2.0.2/t/response/TestAPI/module.pm at line 88
fail #4
# Failed test 35 in
/tmp/modperl2test/mod_perl-2.0.2/t/response/TestAPI/module.pm at line 88
fail #5
# Failed test 40 in
/tmp/modperl2test/mod_perl-2.0.2/t/response/TestAPI/module.pm at line 88
fail #6
# Failed test 45 in
/tmp/modperl2test/mod_perl-2.0.2/t/response/TestAPI/module.pm at line 88
fail #7
# Failed test 50 in
/tmp/modperl2test/mod_perl-2.0.2/t/response/TestAPI/module.pm at line 88
fail #8
# Failed test 55 in
/tmp/modperl2test/mod_perl-2.0.2/t/response/TestAPI/module.pm at line 88
fail #9
# Failed test 60 in
/tmp/modperl2test/mod_perl-2.0.2/t/response/TestAPI/module.pm at line 88
fail #10
# Failed test 65 in
/tmp/modperl2test/mod_perl-2.0.2/t/response/TestAPI/module.pm at line 88
fail #11
[Wed Feb 01 16:49:26 2006] [notice] child pid 23653 exit signal
Segmentation fault (11), possible coredump in
/tmp/modperl2test/mod_perl-2.0.2/t
[Wed Feb 01 16:49:28 2006] [notice] child pid 23652 exit signal
Segmentation fault (11), possible coredump in
/tmp/modperl2test/mod_perl-2.0.2/t
[Wed Feb 01 16:49:29 2006] [info] Child process pid=23671 is exiting
[Wed Feb 01 16:49:29 2006] [info] Child process pid=23671 is exiting -
server push
END in modperl_extra.pl, pid=23671
[Wed Feb 01 16:49:29 2006] [info] removed PID file
/tmp/modperl2test/mod_perl-2.0.2/t/logs/httpd.pid (pid=23648)
[Wed Feb 01 16:49:29 2006] [notice] caught SIGTERM, shutting down
END in modperl_extra.pl, pid=23648
>>>>>
and here is the result of the command "t/REPORT > mybugreport":
>>>>>
-------------8<---------- Start Bug Report ------------8<----------
1. Problem Description:
[DESCRIBE THE PROBLEM HERE]
2. Used Components and their Configuration:
*** mod_perl version 2.000002
*** using /tmp/modperl2test/mod_perl-2.0.2/lib/Apache2/BuildConfig.pm
*** Makefile.PL options:
MP_APR_LIB => aprext
MP_APXS => /usr/sbin/apxs
MP_COMPAT_1X => 1
MP_GENERATE_XS => 1
MP_LIBNAME => mod_perl
MP_USE_DSO => 1
*** /usr/sbin/httpd -V
Server version: Apache/2.0.49
Server built: May 6 2004 07:15:13
Server's Module Magic Number: 20020903:7
Architecture: 32-bit
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_SYSVSEM_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D HTTPD_ROOT="/etc/httpd"
-D SUEXEC_BIN="/usr/sbin/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/sbin/httpd
linux-gate.so.1 => (0x00c6e000)
libpcre.so.0 => /lib/libpcre.so.0 (0x0044e000)
libpcreposix.so.0 => /usr/lib/libpcreposix.so.0 (0x002bb000)
libaprutil-0.so.0 => /usr/lib/libaprutil-0.so.0 (0x004e9000)
libldap.so.2 => /usr/lib/libldap.so.2 (0x0084d000)
liblber.so.2 => /usr/lib/liblber.so.2 (0x00ddc000)
libdb-4.2.so => /lib/tls/libdb-4.2.so (0x0065a000)
libexpat.so.0 => /usr/lib/libexpat.so.0 (0x00d26000)
libapr-0.so.0 => /usr/lib/libapr-0.so.0 (0x00111000)
librt.so.1 => /lib/tls/librt.so.1 (0x00130000)
libm.so.6 => /lib/tls/libm.so.6 (0x00156000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x008d6000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00373000)
libdl.so.2 => /lib/libdl.so.2 (0x007ec000)
libc.so.6 => /lib/tls/libc.so.6 (0x00179000)
libresolv.so.2 => /lib/libresolv.so.2 (0x00432000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x00c9f000)
libssl.so.4 => /lib/libssl.so.4 (0x00e9f000)
libcrypto.so.4 => /lib/libcrypto.so.4 (0x004fe000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00a20000)
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00295000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x002be000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x00b8f000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00d7f000)
libz.so.1 => /usr/lib/libz.so.1 (0x00c6f000)
*** (apr|apu)-config linking info
-laprutil-0 -lldap -llber -ldb-4.2 -lexpat
-lapr-0 -lrt -lm -lcrypt -lpthread -ldl
*** /usr/bin/perl -V
Summary of my perl5 (revision 5.0 version 8 subversion 3) configuration:
Platform:
osname=linux, osvers=2.4.21-4.elsmp, archname=i386-linux-thread-multi
uname='linux tweety.devel.redhat.com 2.4.21-4.elsmp #1 smp fri oct 3
17:52:56 edt 2003 i686 i686 i386 gnulinux '
config_args='-des -Doptimize=-O2 -g -pipe -march=i386 -mcpu=i686
-Dversion=5.8.3 -Dmyhostname=localhost -Dperladmin=root@localhost -Dcc=gcc
-Dcf_by=Red Hat, Inc. -Dinstallprefix=/usr -Dprefix=/usr
-Darchname=i386-linux -Dvendorprefix=/usr -Dsiteprefix=/usr -Duseshrplib
-Dusethreads -Duseithreads -Duselargefiles -Dd_dosuid -Dd_semctl_semun
-Di_db -Ui_ndbm -Di_gdbm -Di_shadow -Di_syslog -Dman3ext=3pm -Duseperlio
-Dinstallusrbinperl -Ubincompat5005 -Uversiononly -Dpager=/usr/bin/less
-isr -Dinc_version_list=5.8.2 5.8.1 5.8.0'
hint=recommended, useposix=true, d_sigaction=define
usethreads=define use5005threads=undef 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 -D_GNU_SOURCE -DTHREADS_HAVE_PIDS
-DDEBUGGING -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm',
optimize='-O2 -g -pipe -march=i386 -mcpu=i686',
cppflags='-D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBUGGING
-fno-strict-aliasing -I/usr/local/include -I/usr/include/gdbm'
ccversion='', gccversion='3.3.3 20040412 (Red Hat Linux 3.3.3-7)',
gccosandvers=''
intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t',
lseeksize=8
alignbytes=4, prototype=define
Linker and Libraries:
ld='gcc', ldflags =' -L/usr/local/lib'
libpth=/usr/local/lib /lib /usr/lib
libs=-lnsl -lgdbm -ldb -ldl -lm -lcrypt -lutil -lpthread -lc
perllibs=-lnsl -ldl -lm -lcrypt -lutil -lpthread -lc
libc=/lib/libc-2.3.3.so, so=so, useshrplib=true, libperl=libperl.so
gnulibc_version='2.3.3'
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic
-Wl,-rpath,/usr/lib/perl5/5.8.3/i386-linux-thread-multi/CORE'
cccdlflags='-fPIC', lddlflags='-shared -L/usr/local/lib'
Characteristics of this binary (from libperl):
Compile-time options: DEBUGGING MULTIPLICITY USE_ITHREADS
USE_LARGE_FILES PERL_IMPLICIT_CONTEXT
Built under linux
Compiled at Apr 15 2004 13:09:17
%ENV:
PERL_LWP_USE_HTTP_10="1"
@INC:
/usr/lib/perl5/5.8.3/i386-linux-thread-multi
/usr/lib/perl5/5.8.3
/usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.2/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.1/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.3
/usr/lib/perl5/site_perl/5.8.2
/usr/lib/perl5/site_perl/5.8.1
/usr/lib/perl5/site_perl/5.8.0
/usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.2/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.3
/usr/lib/perl5/vendor_perl/5.8.2
/usr/lib/perl5/vendor_perl/5.8.1
/usr/lib/perl5/vendor_perl/5.8.0
/usr/lib/perl5/vendor_perl
.
*** Packages of interest status:
Apache2 : -
Apache2::Request : -
CGI : 3.01
ExtUtils::MakeMaker: 6.17
LWP : 5.79
mod_perl : 1.9912
mod_perl2 : -
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 Thu Feb 2 00:51:31 2006 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.
>>>>>
Re: errors in module.t & others when installing mod_perl
Posted by Frank Wiles <fr...@wiles.org>.
On Wed, 01 Feb 2006 18:04:42 -0800
Bennett Haselton <be...@peacefire.org> wrote:
> Yep, turns out that's displayed in the SERVER_SOFTWARE environment
> variable by CGI scripts on the server. How did you know that? :)
I'm magic! ;) Actually it's in the test report you posted earlier,
I just missed it the first time around.
> >Have you removed the mod_perl rpm?
>
> Nope. I was following the steps at:
> http://perl.apache.org/docs/2.0/rename.html#Effects
> which said that the only thing I had to do was run this command:
> find /usr/lib/perl5 -name 'Apache2*' -exec rm -rf {} \;
Yeah those are not the right instructions to be following if you're
attempting to install the way you are. I.e. on a RH/Fedora system
using the rpm installed Apache.
> Do I have to do something else if I want to "remove the mod_perl rpm"?
Just run 'rpm -e mod_perl' on your system.
> Oh OK, I was going by the instructions at
> http://gozer.ectoplasm.org/Talks/mod_perl-2.0-from-cgi-fast.pdf
> since they were the only set of instructions I could find on the
> entire Internet that specified what to type (thank God that Google
> indexes PDF files :) )
> And
> http://perl.apache.org/docs/2.0/user/install/install.html
> says "a correctly built Apache shouldn't require the MP_APR_CONFIG
> option, since MP_APXS should provide the location of this script." I
> thought the version of Apache on my machine was "correctly built"
> since it was, after all, running, but maybe that means something
> other than what I think it means. Does "correctly built" actually
> mean "you built it on your system the old fashioned way, with your
> own compiler"?
Yes, RH uses an "odd" layout compared to most Apache installs.
But if you read the paragraph before it says:
For example RedHat Linux system installs the httpd binary, the apxs
and apr-config scripts (the latter two are needed to build mod_perl)
all in different locations, therefore they configure mod_perl 2.0 as:
% perl Makefile.PL MP_APXS=/path/to/apxs \
MP_APR_CONFIG=/another/path/to/apr-config <other options>
Which should have been the big tip off, but I can see how you got
off track.
> I suppose lots of people must ask, "Why can't the installer be a
> single program that I just run, like on Windows", but why can't it
> be?
Without getting into a bunch of details the main reason is well,
with Windows you have I dunno say 8 different platforms to support
( 98, ME, 2000 Home, 2000 Pro, XP, XP SP1, XP SP2, XP SP3, etc ).
mod_perl runs on many different operating systems, including Linux.
And with Linux alone there are literally thousands of different
distributions. Granted, 99% of them are going to install the
same, but finding all of the various permutations of scenarios is
non-trivial. This doesn't even get into Free/Net/OpenBSD, Solaris,
AIX, HP-UX, etc, etc, etc.
>I have spent three weeks trying to get this working, and every time I
>run into an error, I seek out help and find out the instructions from
>the Web that I was working off of, were incomplete, or wrong, and
>there's always one more thing I have to do first. An installer
>program can do all of this automatically.
I understand your frustration, but when in doubt the "correct"
instructions on are perl.apache.org or the ones you find here on
the mailing list. For the most part anyway, despite the rumors
to the contrary, mod_perl is built by humans which sometimes make
mistakes. ;)
Considering RH/Fedora is so popular, I'll work up a special
instruction document just for them so Google searches will find it
and see about getting it added onto the site.
---------------------------------
Frank Wiles <fr...@wiles.org>
http://www.wiles.org
---------------------------------
Re: errors in module.t & others when installing mod_perl
Posted by Bennett Haselton <be...@peacefire.org>.
At 07:38 PM 2/1/2006 -0600, Frank Wiles wrote:
>On Wed, 01 Feb 2006 17:25:06 -0800
>Bennett Haselton <be...@peacefire.org> wrote:
>
> > Actually I thought that was the very first thing I had done before
> > starting to install mod_perl 2.0.2 on this machine. If you don't
> > uninstall the older version of mod_perl first, you get a more or less
> > clear error message telling you that the problem is that the older
> > version is still present, and you need to get rid of it before
> > proceeding.
> >
> > But, just to make sure, I tried doing it again -- ran the command
> > find /usr/lib/perl5 -name 'Apache2*' -exec rm -rf {} \;
> > to clean out those files, and then did
> > perl Makefile.PL MP_APXS=/usr/sbin/apxs
> >
> > and at the end of all the output I got a bunch of "server dumped
> > core" messages at the end. This didn't happen the last time I did
> > "perl Makefile.PL MP_APXS=/usr/sbin/apxs". Any idea what happened
> > and how to fix it?
>
> I didn't notice this before, but it looks like you're installing
> on a RH/Fedora system.
Yep, turns out that's displayed in the SERVER_SOFTWARE environment variable
by CGI scripts on the server. How did you know that? :)
>Have you removed the mod_perl rpm?
Nope. I was following the steps at:
http://perl.apache.org/docs/2.0/rename.html#Effects
which said that the only thing I had to do was run this command:
find /usr/lib/perl5 -name 'Apache2*' -exec rm -rf {} \;
Do I have to do something else if I want to "remove the mod_perl rpm"?
> I've never tried building mod_perl 2.0.2 against the installed
> httpd RPM, but according to the install docs you need to use this
> instead of just MP_APXS=:
>
> % perl Makefile.PL MP_APXS=/path/to/apxs \
> MP_APR_CONFIG=/another/path/to/apr-config
>
> With MP_APR_CONFIG pointing to wherever apr-config is located on
> your system.
Oh OK, I was going by the instructions at
http://gozer.ectoplasm.org/Talks/mod_perl-2.0-from-cgi-fast.pdf
since they were the only set of instructions I could find on the entire
Internet that specified what to type (thank God that Google indexes PDF
files :) ) And
http://perl.apache.org/docs/2.0/user/install/install.html
says "a correctly built Apache shouldn't require the MP_APR_CONFIG option,
since MP_APXS should provide the location of this script." I thought the
version of Apache on my machine was "correctly built" since it was, after
all, running, but maybe that means something other than what I think it
means. Does "correctly built" actually mean "you built it on your system
the old fashioned way, with your own compiler"?
The problem with even the smallest ambiguities in the instructions is that
as the number of ambiguities increases, the likelihood that you misread at
least one of them, goes up exponentially!
I suppose lots of people must ask, "Why can't the installer be a single
program that I just run, like on Windows", but why can't it be? A lot of
these tests and checks that I keep doing manually (and which lead to the
wrong results if the instructions are ambiguous) seem like things that
could be easily automated, couldn't they? If for no other reason than to
make worthwhile all the work that the developers spent on mod_perl -- after
all that, how many people give up even trying to get it installed? I have
spent three weeks trying to get this working, and every time I run into an
error, I seek out help and find out the instructions from the Web that I
was working off of, were incomplete, or wrong, and there's always one more
thing I have to do first. An installer program can do all of this
automatically.
-Bennett
bennett@peacefire.org http://www.peacefire.org
(425) 497 9002
Re: errors in module.t & others when installing mod_perl
Posted by Bennett Haselton <be...@peacefire.org>.
At 04:41 PM 2/3/2006 -0600, Frank Wiles wrote:
>On Fri, 03 Feb 2006 14:35:05 -0800
>Bennett Haselton <be...@peacefire.org> wrote:
>
> > I also tried doing:
> > rpm -e mod_perl
> > and I got:
> > error: Failed dependencies:
> > mod_perl is needed by (installed)
> > psa-7.5.0-fc2.build75041208.20
> >
> > I am completely stuck again, sorry!
>
> Well you're trying to run this in an environment with Plesk, that
> is going to cause you untold amount of headaches. Control panels
> like Plesk, cPanel, etc. aren't built to support more advanced
> setups.
>
> Here are some suggestions:
>
> 1) If you aren't using Plesk then uninstall it with:
>
> rpm -e psa
> rpm -e mod_perl
>
> 2) If you are wanting to use it for some sites, but not your mod_perl
> ones you can install Apache into another location from source
> and compile mod_perl against that.
I'm extremely reluctant to get rid of Plesk since I would forfeit any
chance of ever getting help from my ISP again if I needed something else.
Here's what I don't understand:
1) Are you saying that I get all these "core dump" messages when I run
"perl Makefile.PL MP_APXS=/usr/sbin/apxs
MP_APR_CONFIG=/usr/bin/apr-config", because the mod_perl RPM is already
installed? But in that case, why didn't I get all those error messages
when I ran "perl Makefile.PL MP_APXS=/usr/sbin/apxs
MP_APR_CONFIG=/usr/bin/apr-config" the first time?
2) If I can't *remove* the mod_perl rpm because the Plesk rpm is dependent
on it, is it not possible to just *upgrade* the mod_perl rpm, so that it's
never "missing" and doesn't break any dependencies?
-Bennett
bennett@peacefire.org http://www.peacefire.org
(425) 497 9002
Re: errors in module.t & others when installing mod_perl
Posted by Frank Wiles <fr...@wiles.org>.
On Fri, 03 Feb 2006 14:35:05 -0800
Bennett Haselton <be...@peacefire.org> wrote:
> I also tried doing:
> rpm -e mod_perl
> and I got:
> error: Failed dependencies:
> mod_perl is needed by (installed)
> psa-7.5.0-fc2.build75041208.20
>
> I am completely stuck again, sorry!
Well you're trying to run this in an environment with Plesk, that
is going to cause you untold amount of headaches. Control panels
like Plesk, cPanel, etc. aren't built to support more advanced
setups.
Here are some suggestions:
1) If you aren't using Plesk then uninstall it with:
rpm -e psa
rpm -e mod_perl
2) If you are wanting to use it for some sites, but not your mod_perl
ones you can install Apache into another location from source
and compile mod_perl against that.
---------------------------------
Frank Wiles <fr...@wiles.org>
http://www.wiles.org
---------------------------------
Re: errors in module.t & others when installing mod_perl
Posted by Bennett Haselton <be...@peacefire.org>.
At 06:30 PM 2/1/2006 -0800, Tyler MacDonald wrote:
>Bennett Haselton <be...@peacefire.org> wrote:
> > But, just to make sure, I tried doing it again -- ran the command
> > find /usr/lib/perl5 -name 'Apache2*' -exec rm -rf {} \;
> > to clean out those files, and then did
> > perl Makefile.PL MP_APXS=/usr/sbin/apxs
>
> There's also files named "mod_perl.pm", and "ModPerl*", installed
> by
>mod_perl2. Look for a file called ".packlist" in a "mod_perl" or
>"mod_perl2"
>directory (or both if you've installed both); that should contain a list
>of
>every file that "make install" installed. Then you can just do something
>like:
>
> cat
> /opt/apache2/perl5lib/i486-linux-gnu-thread-multi/auto/mod_perl2/.packlist
> | xargs rm -vf
>
> To remove those files.
OK I found the .packlist file at
/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi/auto/mod_perl/.packlist
so, I ran the command:
cat
/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi/auto/mod_perl/.packlist
| xargs rm -vf
and then went back to my mod_perl-2.0.2 directory and did:
perl Makefile.PL MP_APXS=/usr/sbin/apxs MP_APR_CONFIG=/usr/bin/apr-config
and I still got the long string of "server dumped core again" messages.
I also tried doing:
rpm -e mod_perl
and I got:
error: Failed dependencies:
mod_perl is needed by (installed) psa-7.5.0-fc2.build75041208.20
I am completely stuck again, sorry!
-Bennett
bennett@peacefire.org http://www.peacefire.org
(425) 497 9002
Re: errors in module.t & others when installing mod_perl
Posted by Tyler MacDonald <ty...@yi.org>.
Bennett Haselton <be...@peacefire.org> wrote:
> But, just to make sure, I tried doing it again -- ran the command
> find /usr/lib/perl5 -name 'Apache2*' -exec rm -rf {} \;
> to clean out those files, and then did
> perl Makefile.PL MP_APXS=/usr/sbin/apxs
There's also files named "mod_perl.pm", and "ModPerl*", installed by
mod_perl2. Look for a file called ".packlist" in a "mod_perl" or "mod_perl2"
directory (or both if you've installed both); that should contain a list of
every file that "make install" installed. Then you can just do something
like:
cat /opt/apache2/perl5lib/i486-linux-gnu-thread-multi/auto/mod_perl2/.packlist | xargs rm -vf
To remove those files.
- Tyler
Re: errors in module.t & others when installing mod_perl
Posted by Frank Wiles <fr...@wiles.org>.
On Wed, 01 Feb 2006 17:25:06 -0800
Bennett Haselton <be...@peacefire.org> wrote:
> Actually I thought that was the very first thing I had done before
> starting to install mod_perl 2.0.2 on this machine. If you don't
> uninstall the older version of mod_perl first, you get a more or less
> clear error message telling you that the problem is that the older
> version is still present, and you need to get rid of it before
> proceeding.
>
> But, just to make sure, I tried doing it again -- ran the command
> find /usr/lib/perl5 -name 'Apache2*' -exec rm -rf {} \;
> to clean out those files, and then did
> perl Makefile.PL MP_APXS=/usr/sbin/apxs
>
> and at the end of all the output I got a bunch of "server dumped
> core" messages at the end. This didn't happen the last time I did
> "perl Makefile.PL MP_APXS=/usr/sbin/apxs". Any idea what happened
> and how to fix it?
I didn't notice this before, but it looks like you're installing
on a RH/Fedora system. Have you removed the mod_perl rpm?
I've never tried building mod_perl 2.0.2 against the installed
httpd RPM, but according to the install docs you need to use this
instead of just MP_APXS=:
% perl Makefile.PL MP_APXS=/path/to/apxs \
MP_APR_CONFIG=/another/path/to/apr-config
With MP_APR_CONFIG pointing to wherever apr-config is located on
your system.
---------------------------------
Frank Wiles <fr...@wiles.org>
http://www.wiles.org
---------------------------------
Re: errors in module.t & others when installing mod_perl
Posted by Bennett Haselton <be...@peacefire.org>.
At 07:19 PM 2/1/2006 -0600, Frank Wiles wrote:
>On Wed, 01 Feb 2006 17:08:13 -0800
>Bennett Haselton <be...@peacefire.org> wrote:
>
> > Now I'm trying to install mod_perl 2.0.2 on a different machine
> > running Apache/2.0.49. When I run "make test", this is the chart of
> > errors that I get at the end:
>
> > *** Packages of interest status:
> >
> > Apache2 : -
> > Apache2::Request : -
> > CGI : 3.01
> > ExtUtils::MakeMaker: 6.17
> > LWP : 5.79
> > mod_perl : 1.9912
> > mod_perl2 : -
>
> It looks like you haven't removed an old mod_perl 1.99 installation
> on this system. You'll need to do that before trying to install
> 2.0.2. You can find the instructions here:
>
> http://perl.apache.org/docs/2.0/rename.html#Effects
Actually I thought that was the very first thing I had done before starting
to install mod_perl 2.0.2 on this machine. If you don't uninstall the
older version of mod_perl first, you get a more or less clear error message
telling you that the problem is that the older version is still present,
and you need to get rid of it before proceeding.
But, just to make sure, I tried doing it again -- ran the command
find /usr/lib/perl5 -name 'Apache2*' -exec rm -rf {} \;
to clean out those files, and then did
perl Makefile.PL MP_APXS=/usr/sbin/apxs
and at the end of all the output I got a bunch of "server dumped core"
messages at the end. This didn't happen the last time I did "perl
Makefile.PL MP_APXS=/usr/sbin/apxs". Any idea what happened and how to fix
it?
*******
[warning] mod_perl dso library will be built as mod_perl.so
[warning] You'll need to add the following to httpd.conf:
[warning]
[warning] LoadModule perl_module modules/mod_perl.so
[warning]
[warning] depending on your build, mod_perl might not live in
[warning] the modules/ directory.
[warning] Check the results of
[warning]
[warning] $ /usr/sbin/apxs -q LIBEXECDIR
[warning]
[warning] and adjust the LoadModule directive accordingly.
[ error] oh darn, server dumped core
[ error] for stacktrace, run: gdb /usr/sbin/httpd -core
/tmp/modperl2test/mod_perl-2.0.2/t/core.24650
[ error] oh crap, server dumped core again
[ error] for stacktrace, run: gdb /usr/sbin/httpd -core
/tmp/modperl2test/mod_perl-2.0.2/t/core.16231
[ error] oh darn, server dumped core again
[ error] for stacktrace, run: gdb /usr/sbin/httpd -core
/tmp/modperl2test/mod_perl-2.0.2/t/core.25303
[ error] oh rats, server dumped core again
[ error] for stacktrace, run: gdb /usr/sbin/httpd -core
/tmp/modperl2test/mod_perl-2.0.2/t/core.22978
[ error] oh shucks, server dumped core again
[ error] for stacktrace, run: gdb /usr/sbin/httpd -core
/tmp/modperl2test/mod_perl-2.0.2/t/core.15800
[ error] oh rats, server dumped core again
[ error] for stacktrace, run: gdb /usr/sbin/httpd -core
/tmp/modperl2test/mod_perl-2.0.2/t/core.15604
[ error] oh dangnabit, server dumped core again
[ error] for stacktrace, run: gdb /usr/sbin/httpd -core
/tmp/modperl2test/mod_perl-2.0.2/t/core.18701
[ error] oh jeez, server dumped core again
[ error] for stacktrace, run: gdb /usr/sbin/httpd -core
/tmp/modperl2test/mod_perl-2.0.2/t/core.23653
[ error] oh golly, server dumped core again
[ error] for stacktrace, run: gdb /usr/sbin/httpd -core
/tmp/modperl2test/mod_perl-2.0.2/t/core.23666
[ error] oh dangnabit, server dumped core again
[ error] for stacktrace, run: gdb /usr/sbin/httpd -core
/tmp/modperl2test/mod_perl-2.0.2/t/core.23652
[ error] oh gosh, server dumped core again
[ error] for stacktrace, run: gdb /usr/sbin/httpd -core
/tmp/modperl2test/mod_perl-2.0.2/t/core.18813
[ error] oh gosh, server dumped core again
[ error] for stacktrace, run: gdb /usr/sbin/httpd -core
/tmp/modperl2test/mod_perl-2.0.2/t/core.24877
Re: errors in module.t & others when installing mod_perl
Posted by Frank Wiles <fr...@wiles.org>.
On Wed, 01 Feb 2006 17:08:13 -0800
Bennett Haselton <be...@peacefire.org> wrote:
> Now I'm trying to install mod_perl 2.0.2 on a different machine
> running Apache/2.0.49. When I run "make test", this is the chart of
> errors that I get at the end:
> *** Packages of interest status:
>
> Apache2 : -
> Apache2::Request : -
> CGI : 3.01
> ExtUtils::MakeMaker: 6.17
> LWP : 5.79
> mod_perl : 1.9912
> mod_perl2 : -
It looks like you haven't removed an old mod_perl 1.99 installation
on this system. You'll need to do that before trying to install
2.0.2. You can find the instructions here:
http://perl.apache.org/docs/2.0/rename.html#Effects
---------------------------------
Frank Wiles <fr...@wiles.org>
http://www.wiles.org
---------------------------------