Hi!
I have apache 1.3.12 and the latest DBI running on Sparc Solaris 2.7. when
i try to run an embedded perl script that makes use of the DBI i get the
following error:
ld.so.1: perl: fatal: relocation error: file
/usr/local/lib/perl5/site_perl/5.005/sun4-solaris/auto/DBD/mysql/mysql.so: symbol
m
On Fri, 14 Jan 2000, Cere M. Davis wrote:
> I have found the weirdest problem with (I think) DBD::Ingres,
> DBI::trace() and Apache::DBI when the DBI::trace level is set to 1 or 0.
>
> I get an error in the Apache error_logs that says:
>
> unitialized value at
> /uns/mind/usr/local/perl5/
I have found a weird problem related to DBD::Ingres,
DBI::trace() and Apache::DBI when the DBI::trace level is set to 1 or 0.
I get an error in the Apache error_logs that says:
unitialized value at
/uns/mind/usr/local/perl5/lib/site_perl/5.005/alpha-dec_osf/
DBD/Ingres.pm line 85
OTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Newbie problem with DBI under modperl
>
> > try setting trace to level 6 for greater detail...
> > BTW, you can also separate the trace output from your error_log via
> > DBI->trace(6,"/
> try setting trace to level 6 for greater detail...
> BTW, you can also separate the trace output from your error_log via
> DBI->trace(6,"/path/to/trace.log");
> from within your handler or script.
Cool, I did that - thanks for the pointer! Of course,
the output is even more mysterious now to m
: Dan Mahoney [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, October 28, 1999 10:05 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Newbie problem with DBI under modperl
>
> > Hopefully you have a startup script you use to load various mo
> Hopefully you have a startup script you use to load various modules
> into the server memory. If so, could you add the following to it:
>
> BEGIN {
> $ENV{DBI_TRACE} = 2;
> }
>
> This will cause DBI and Apache::DBI (as the case may be) to put a LOT
> of information into the error file. Thi
Dan Mahoney <[EMAIL PROTECTED]> wrote:
>I've got a weird problem here involving DBI under
>mod_perl.
>
[snip]
Hopefully you have a startup script you use to load various modules
into the server memory. If so, could you add the following to it:
BEGIN {
$ENV{DBI_TRACE} = 2;
}
This will cause D
I've got a weird problem here involving DBI under
mod_perl.
I have a simple Perl script that works from the
command line:
-
#!/usr/local/bin/perl
use strict;
use DBI;
my ($dbh, $sth, $f, $head) = undef;
$dbh = DBI->connect("dbi:m
