in reply to Re^2: 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?

From looking at the Apache::DBI source code, the error message Apache.pm was not loaded is raised if it doesn't detect a true value in $INC{'Apache.pm'}. This indicates to me that you're not running your script under mod_perl at all, or (really remote) that Apache.pm fails to load. Maybe put use Apache; into your main script, just for a test.

Replies are listed 'Best First'.
Re^4: Should I upgrade from mod_perl 1.0 to 2.0? and if so, how?
by MashMashy (Sexton) on Feb 17, 2009 at 14:58 UTC
    done, and done - if by "main script" you mean "startup.pl", I did so, and got:

    "Can't locate Apache.pm in @INC" etc etc etc.

    Am I missing an install?

      Again, looking at the Apache::DBI source code, it seems that Apache.pm should be there once you're running under mod_perl (1), so, the circumstances point to you not running under mod_perl.

        that gateway line ticks over, though, so there's an indication that I am. what could I do to check if I am or not?
        I also see this: in that info page:
        MOD_PERL 1.0 Note that this module needs mod_perl-1.08 or higher, apache_1.3.0 or higher and that mod_perl needs to be configured with the appropriate call-back hooks:

        PERL_CHILD_INIT=1 PERL_STACKED_HANDLERS=1
        How can I check if those hooks are implemented? could this error be caused by that?