Red Hat Bugzilla – Bug 104888
Installing perl-5.6.1-36.1.71 breaks mod_perl-1.24_01-2
Last modified: 2006-02-21 13:58:41 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
After installing perl-5.6.1-36.1.71 (and apache-1.3.27-2.7.1.i386.rpm,
mod_ssl-2.8.12-2.7.i386.rpm and related dependancies, but I don't think they are
involved), a mod_perl enabled apache refuses to start, reporting
Can't locate strict.pm in @INC (@INC contains: /usr/lib/perl5/5.6.0/i386-linux
/usr/lib/perl5/site_perl/5.6.0 /usr/lib/perl5/site_perl . /etc/httpd/
/etc/httpd/lib/perl) at /usr/lib/perl5/site_perl/5.6.0/i386-linux/Apache.pm line 3.
I suspect that this is becasue the perl upgrade removed the old
/usr/lib/perl5/5.6.0 directory but that this is hard-coded into the search path
in the mod_perl binary.
Actually I's assume a new 5.6.1-based mod_perl is actually needed to match the
new stand-alone perl.
This problem may additionally apply to RH7.2 and RH7.3.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.attempt to restart a mod_perl-using apache
Actual Results: Apache should restart
Expected Results: Apache doesn't restart
Go get the SRPM for mod_perl and do:
rpm --rebuild mod_perl-1.24_01-2.src.rpm
rpm -Uvh --force mod_perl-1.24_01-2.i386.rpm
and you are good to go.
*** This bug has been marked as a duplicate of 104875 ***
*** Bug 104943 has been marked as a duplicate of this bug. ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.