[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Broken perl environment with libapache-mod-perl2 and apache2



Hello,

I'm wondering if anyone is running libapache-mod-perl2 from sarge.  I'm
getting some odd errors which look to be related to an error in the perl
environment.  I'm trying to use ModPerl::Registry, formerly
Apache::Registry with apache2.  Per the instructions at perl.apache.org,
I've made a http.conf which looks like...

# mod-perl cgi scripts to be executed by ModPerl::Registry
PerlModule ModPerl::Registry
Alias /cgi-perl/ /usr/local/lib/cgi-perl/
<Location /cgi-perl>
SetHandler  perl-script
PerlResponseHandler ModPerl::Registry
# PerlOptions +ParseHeaders
# PerlOptions -GlobalRequest
Options +ExecCGI
</Location>

When I attempt to start apache2 I get the following error message.


Starting web server: Apache2[Sun Jul 18 22:33:14 2004] [warn]
NameVirtualHost *:80 has no VirtualHosts
[Sun Jul 18 22:33:15 2004] [error] Can't locate ModPerl/Registry.pm in
@INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.3
/usr/local/share/perl/5.8.3 /usr/lib/perl5 /usr/share/perl5
/usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .
/etc/apache2/ /etc/apache2/lib/perl) at (eval 1) line 3.\n
[Sun Jul 18 22:33:15 2004] [error] Can't load Perl module
ModPerl::Registry for server eagle.cgnet.ca:0, exiting...\n

Modifying the PerlModule line to ...

PerlModule Apache2::ModPerl::Registry

Seems to do a better job of loading the module, but the startup dies
with...

[Sun Jul 18 22:36:13 2004] [error] Base class package
"ModPerl::RegistryCooker" is empty.\n    (Perhaps you need to 'use' the
module which defines that package first.)\n at
/usr/lib/perl5/Apache2/ModPerl/Registry.pm line 11\nBEGIN
failed--compilation aborted at /usr/lib/perl5/Apache2/ModPerl/Registry.pm
line 11.\nCompilation failed in require at (eval 1) line 3.\n
[Sun Jul 18 22:36:13 2004] [error] Can't load Perl module
Apache2::ModPerl::Registry for server eagle.cgnet.ca:0, exiting...\n

Now this seems incorrect to me to have use lines in httpd.conf, but I may
be wrong.  Has anyone else experienced this, or know how to fix the
environment?





Reply to: