in reply to Re^6: Apache::DBI "cannot find apache.pm" failure - Should I upgrade from mod_perl 1.0 to 2.0? and if so, how?
in thread Apache::DBI "cannot find apache.pm" failure - Should I upgrade from mod_perl 1.0 to 2.0? and if so, how?

I would assume that it either means that mod_perl is not installed, or that it is not available to you, or that we both have misconceptions about how things are with mod_perl in general.

I recommend, again, that you consult with whoever is administrating your machine. That person should be able to tell you how and where to find the things you need to enable mod_perl for your script, or should be able to tell you that mod_perl is unavailable to you. There is little I can do from here to navigate you through whatever tech support your machine administrator provides you.

  • Comment on Re^7: Apache::DBI "cannot find apache.pm" failure - Should I upgrade from mod_perl 1.0 to 2.0? and if so, how?

Replies are listed 'Best First'.
Re^8: Apache::DBI "cannot find apache.pm" failure - Should I upgrade from mod_perl 1.0 to 2.0? and if so, how?
by MashMashy (Sexton) on Feb 17, 2009 at 15:23 UTC
    I've done that, and they say that mod_perl is installed. I have directories in httpd.conf marked as such:
    SetHandler perl-script Options +ExecCGI PerlHandler ModPerl::Registry
    and those directories compile and run .pl files.
    Doesn't that mean that modperl is working?

    (also, CPAN says 'mod_perl is up to date'. that'd check for it, right?

      Well duh. Then maybe consider checking what difference is between the scripts that appear to work, and your scripts that don't appear to work. Or maybe just escalate the problem to your machine (or webserver) administrators, if you feel unable to resolve the differences between the working and the non-working scripts yourself.