I have had the same error with mysql, which really had nothing to do with
Apache::DBI.  The problem was the shared library file, the .so, was not installed in
the correct directory.  Various ways exist fix this including recompiling the DBD
module with -static, or, more simply, copying the .so file into the shared libraries
directory.

I hope this helps.

--
Doug Kyle - Information Systems
Grand Rapids Public Library
"Try to imagine all life as you know it stopping instantaneously and every molecule
in your body exploding at the speed of light." - Dr. Egon Spengler



"Cere M. Davis" wrote:

> I am trying to get the DBI::Ingres stuff to work with Apache::DBI.
>
> Once the server tries to open the inital connections through the
> startup.pl file with the "Apache::DBI->connect_on_init" command it throws
> an error message like this:
>
> 168 Apache::DBI             PerlChildInitHandler
> [Fri Jan  7 12:46:35 2000] [error] install_driver(Ingres) failed: Can't
> load
> '/uns/mind/usr/local/perl5/lib/site_perl/5.005/alpha-dec_osf/auto/DBD/Ingres/Ing
> res.so'
> for module DBD::Ingres: dlopen: cannot load
> /uns/mind/usr/local/perl5/lib/site_perl/5.005/alpha-dec_osf/auto/DBD/Ingres/Ingr
> es.so
> at /uns/mind/usr/local/perl5/lib/5.00503/alpha-dec_osf/DynaLoader.pm
> line 169.
>
>  at (eval 15) line 3
>
>  at /uns/mind/usr/local/perl5/lib/site_perl/5.005/Apache/DBI.pm line 138
>
> in the error_log when I run httpsd -X (single thread mode).
>
> I can run the DBI drivers to ingres with no problems outside
>
> of Apache just not with the Apache mod_perl stuff.
>
> Does anyone know what's going on here?  I expect that DynaLoader
>
> is used to load the DBI standalone stuff - and that works fine -
>
> so why is it that DynaLoader would have trouble loading Ingres.so
>
> when requested through Apache::DBI?
>
> -Cere
>
> *********************************
> Cere Davis                      *
> Systems Administrator           *
> MCIS University of Washington   *
> 206.221.4717                    *
> [EMAIL PROTECTED]           *
> *********************************

Reply via email to