You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by "Young, Darren" <Da...@ChicagoGSB.edu> on 2005/01/19 21:58:56 UTC
Problem on RedHat Enterprise 3.0
I have a RedHat Enterprise 3.0 system that doesn't seem to want to work. The same procedure I followed worked on another system (RHEL 3.0) but isn't on this one.
I have the stock Apache 2.0.46 rpm installed and a pretty generic httpd.conf file, at least, it's generic in the fact that it's right from the RPM with few chanegs.
The RH Perl 5.8.0 rpm is installed and perl works fine for regular scripts and cgi's. I installed their (RedHat) mod_perl rpm (1.99_09) which adds the file /etc/httpd/conf.d/perl.conf that's included by the main httpd.conf.
I added the following for /perl-status as a test:
<Location /perl-status>
SetHandler perl-script
PerlResponseHandler Apache::Status
Order allow,deny
Allow from all
Deny from none
</Location>
The browser gets a 500 page and the apache error log has this in it:
[Wed Jan 19 14:34:18 2005] [error] [client 67.184.77.67] Can't locate object method "print" via package "Apache::RequestRec" at /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Apache/Status.pm line 144.!
Tried uninstalling the mod_perl rpm and reinstalling it. Same thing. Some other RPM or perl module I'm missing? Maybe I had another required module already installed on the other system I have working.
Oh, and the server signature says:
<span>Apache/2.0.46 (Red Hat) mod_perl/1.99_09 Perl/v5.8.0 DAV/2 PHP/4.3.2</span>
Any thoughts or suggestions would be most appreciated.
Thanks,
Darren Young
University of Chicago
Graduate School of Business
Re: Problem on RedHat Enterprise 3.0
Posted by Jay Scherrer <ja...@scherrer.com>.
Instead of mv'ing your Apache lib, couldn't you not include it and
just stipulate the libs you want to use in the startup.pl script?
Jay Scherrer
On Wednesday 19 January 2005 03:27 pm, Aaron Hawryluk wrote:
> I didn't get the full text of this message, but if the apache
> modules aren't loading right and this is a mod_perl 1.99 install on
> Apache2, I just had the exact same problem... mod_perl simply
> wouldn't load. There were all kinds of complaints from perl about
> how various Apache:: and ModPerl:: modules couldn't be found...
> Turned out to be a conflict between the site_perl and vendor_perl
> libraries. It was fixed by the following:
>
> mv /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Apache
> /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Apache.bak
>
> This causes the search for the Apache modules to default to
> vendor_perl instead of site. Fixes it nicely. May confuse CPAN,
> though I haven't checked yet.
>
> My problem? My company is actually paying for a RHEL service
> contract, and they have neither detected nor patched this issue
> yet. Ah, if only we could've gone with Fedora...
>
> -----Original Message-----
> From: Jay Scherrer [mailto:jay@scherrer.com]
> Sent: Wednesday, January 19, 2005 4:01 PM
> To: modperl@perl.apache.org
> Subject: Re: Problem on RedHat Enterprise 3.0
>
> Darren Young,
>
> Have you checked to see if Apache::RequestRec was installed?
> Try CPANing the installation of Bundle::Apache. It looks like your
> mod_perl is looking for the Lib ok but it's not installed.
>
>
> Jay Scherrer
>
> On Wednesday 19 January 2005 12:58 pm, Young, Darren wrote:
> > Apache::RequestRec
RE: Problem on RedHat Enterprise 3.0
Posted by Aaron Hawryluk <we...@calgarysun.com>.
I didn't get the full text of this message, but if the apache modules aren't
loading right and this is a mod_perl 1.99 install on Apache2, I just had the
exact same problem... mod_perl simply wouldn't load. There were all kinds
of complaints from perl about how various Apache:: and ModPerl:: modules
couldn't be found... Turned out to be a conflict between the site_perl and
vendor_perl libraries. It was fixed by the following:
mv /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Apache
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Apache.bak
This causes the search for the Apache modules to default to vendor_perl
instead of site. Fixes it nicely. May confuse CPAN, though I haven't
checked yet.
My problem? My company is actually paying for a RHEL service contract, and
they have neither detected nor patched this issue yet. Ah, if only we
could've gone with Fedora...
-----Original Message-----
From: Jay Scherrer [mailto:jay@scherrer.com]
Sent: Wednesday, January 19, 2005 4:01 PM
To: modperl@perl.apache.org
Subject: Re: Problem on RedHat Enterprise 3.0
Darren Young,
Have you checked to see if Apache::RequestRec was installed?
Try CPANing the installation of Bundle::Apache. It looks like your mod_perl
is looking for the Lib ok but it's not installed.
Jay Scherrer
On Wednesday 19 January 2005 12:58 pm, Young, Darren wrote:
> Apache::RequestRec
Re: Problem on RedHat Enterprise 3.0
Posted by Jay Scherrer <ja...@scherrer.com>.
Darren Young,
Have you checked to see if Apache::RequestRec was installed?
Try CPANing the installation of Bundle::Apache. It looks like your
mod_perl is looking for the Lib ok but it's not installed.
Jay Scherrer
On Wednesday 19 January 2005 12:58 pm, Young, Darren wrote:
> Apache::RequestRec
Re: Problem on RedHat Enterprise 3.0
Posted by Todd Grimason <to...@slack.net>.
* Perrin Harkins <pe...@elem.com> [2005-01-19 21:14]:
> Young, Darren wrote:
> > I installed their (RedHat) mod_perl rpm (1.99_09)
>
> I understand that you're trying to stick with your vendor's packaging
> system, but that's a really old version of mod_perl 2. It was released
> about two years ago, and there have been two years worth of bug fixes
I just tried fighting this battle recently, in the end deciding to
just run a custom apache1.3/mp1, with the perhaps overly-optimistic
plan of hoping RedHat releases a newer MP2 (after release) which I can
then install (in parallel) with RPMs (I installed MP1 in /usr/local).
> > [Wed Jan 19 14:34:18 2005] [error] [client 67.184.77.67] Can't locate
> > object method "print" via package "Apache::RequestRec" at
> > /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Apache/Status.pm
> > line 144.!
I wish I had kept notes - I hit the same problem - I believe it's as
Perrin mentioned, it's an older version of Apache::Status. I'm vaguely
thinking I altered startup.pl and added
use Apache2;
use Apache::compat;
which I *think* did the trick. But then I hit other confusing issues
trying to figure out what the status of everything was - libapreq,
whether or not Apache::DBI was fully working, etc., and didn't have
time to test everything enough myself so I fell back to MP1.
I found it difficult to find comprehensive, updated instructions for
handling a move from MP1 to MP2. I'd guess once MP2's released all
that will catch up, but at this point I basically chickened out.
Good luck! (and of course I hope people will point out any errors in
my advice to you...)
-Todd
>
> Can you tell us what version of Apache::Status that is? I'm not sure
> there even was an Apache::Status port for mod_perl 2 at the time. Could
> this be left over from a mod_perl 1 installation you have on that box?
>
> - Perrin
--
______________________________
toddgrimason*todd-AT-slack.net
Re: Problem on RedHat Enterprise 3.0
Posted by Perrin Harkins <pe...@elem.com>.
Young, Darren wrote:
> I installed their (RedHat) mod_perl rpm (1.99_09)
I understand that you're trying to stick with your vendor's packaging
system, but that's a really old version of mod_perl 2. It was released
about two years ago, and there have been two years worth of bug fixes
since then. It's hard for the people on the list to effectively support
users who are running what is essentially an alpha version of mod_perl
2. Please consider building your own RPM of the most recent version, or
bugging Red Hat to package something more up-to-date.
> [Wed Jan 19 14:34:18 2005] [error] [client 67.184.77.67] Can't locate
> object method "print" via package "Apache::RequestRec" at
> /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Apache/Status.pm
> line 144.!
Can you tell us what version of Apache::Status that is? I'm not sure
there even was an Apache::Status port for mod_perl 2 at the time. Could
this be left over from a mod_perl 1 installation you have on that box?
- Perrin