Re: DBI and Apache::DBI
I S wrote: Hi all, I have some questions with DBI. a) I don't understand why the database sometimes gets dropped. It happens randomly but frequently. could not prepare: Database disconnected at /dssweb/httpd/cgi-bin/feeds/viewReport line 157. b) I built mod_perl and apache with EVERYTHING=1. Should I expect DBI.pm appear in Apache directory? For some reason, it doesn't get there. Or should I add DBI module under Apached directory? If so, how. I have my own version of Perl under home directory. Thanks, Isarin Hello, DBI.pm should normaly be in the tree of your perl-installation (where all global modules are stored). Your httpd.conf should contain the following lines in the config of your domain: LoadModule perl_module modules/mod_perl.so PerlModule Apache2 PerlModule Apache::DBI Perhaps it would be easier for us to help you, if you would include the necessary part of your script. Erik - ArgonSoft GmbH | Im Ermlisgrund 3 | 76337 Waldbronn Tel: +49 7243 71520 | Fax: +49 7243 715222 | http://www.argonsoft.de -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
mod_perl 1.99_13 / apache 2.0.x / mysql 4.1.1 - connection problem
Hello,
we migrated to mysql 4.1.1. Now, when my perl-script tries to connect to
the mysql-server, the following error occurs:
--
Error message:
DBI
connect('database=mydatabase;mysql_client_found_rows=0;host=myhost.net','myuser',...)
failed: Client does not support authentication protocol requested by
server; consider upgrading MySQL client at
/mypath/skripts/cgi-bin/test.pl line 8
---
I think, the problem has to do with mod_perl, because when I run the
script on the console, everything works fine. If I run the script
without mod_perl (over the web with apache), the script also works
without any problems. The script also works with mod_perl connecting to
a mysql 4.0.x - version. Only connecting a 4.1.1-version of mysql
produces the error above.
It is not a problem in general; I've got two webserver with the same
script running mod_perl. On one, there is no problem, on the other the
problem drives me mad.
My configuration:
-
System with problem:
FreeBSD 5.1-RELEASE #3
Apache/2.0.49
mod_perl/1.99_13
Perl/v5.8.0
mysql-4.1.1 Client
DBD::mysql 2.9003
System without problem:
FreeBSD 5.2-RELEASE #0
Apache/2.0.48
mod_perl/1.99_13
Perl/v5.8.2
mysql-4.1.1 Client
DBD::mysql 2.9003
The system with the problem was updated to get rid of the problem from:
Apache/2.0.46
The test-script:
#!/usr/bin/perl
use strict;
use CGI;
# Connect to the database
use Apache::DBI;
my $dbh =
DBI-connect(dbi:mysql:database=mydatabase;mysql_client_found_rows=0;host=myhost.net,myuser,
mypass, {RaiseError = 1});
my ($info) = $dbh-selectrow_array(SELECT info FROM mytable WHERE id=2);
print $cgi-header(-expires='-1d');
print $info;
(The name, host, password and username are not the real values)
Hope someone of you has an idea.
Thanks for all answers.
Erik
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: mod_perl 1.99_13 / apache 2.0.x / mysql 4.1.1 - connection problem
Garrison Hoffman wrote: On Tue, 2004-05-11 at 05:02, Erik Scholtz, ArgonSoft GmbH wrote: failed: Client does not support authentication protocol requested by server; consider upgrading MySQL client at This may help: http://dev.mysql.com/doc/mysql/en/Old_client.html Thanks for your answer. This makes SQL use the old authentication and for fast solution this will be ok. But why does mod_perl not support the new authentication-style? Erik - ArgonSoft GmbH | Im Ermlisgrund 3 | 76337 Waldbronn Tel: +49 7243 71520 | Fax: +49 7243 715222 | http://www.argonsoft.de -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
