Re^3: Apache::DBI "cannot find apache.pm" failure - Should I upgrade from mod

The deal is, you are running alpha software that Red Hat should never have packaged. The whole 1.9* line is a pre-release of 2.0 and it no longer works. That's why you can't get this to go. Apache::DBI works with 2.*, so get a recent version. I do recommend using the latest source and making an RPM from your own build, but if you have to use an external RPM try to find a source RPM from a more recent Red Hat release that you can recompile for your platform.

Comment on Re^3: 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^4: 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 17:51 UTC
like I asked the other fellow, I'm trying to figure out how to do this, without having to reinstall everything. I just want to get mod_perl 2 to 'go'. I think this involves uninstalling MP1, installing MP2, and rebuilding apache. Figuring out how to do this, however, eludes me. It seems like it would be easy, but I can't find a 'how to', and billable support seems excessive (although I'll do it if I need to). Any idea on where I can find a how-to?	[reply]
Re^5: Apache::DBI "cannot find apache.pm" failure - Should I upgrade from mod_perl 1.0 to 2.0? and if so, how? by perrin (Chancellor) on Feb 17, 2009 at 18:24 UTC
You don't have mod_perl 1. You have a broken alpha version of mod_perl 2. You have to install a real mod_perl 2 to make this work. Since you're using rpms, uninstalling your broken mod_perl should be simple: find the mod_perl rpm and remove it. Then you need to either install from source as described in the mod_perl docs or find a source rpm for a recent release.	[reply]