Menu
▾
▴
Re: [log4perl-devel] Log::Log4perl::Appender::DBI appender not working
|
From: Mike S. <m...@pe...> - 2009-02-12 08:55:29
|
On Thu, 12 Feb 2009, wei...@gm... wrote: > When I saw "Log4perl: DBI appender failed to reconnect to database > after 1 attempt at ./tests/testDbCon.pl line 21", I thought it was the > database connection issue. Maybe it'd nice that the actual DBI error > was captured. Yeah, that was a misleading error message, I've fixed it in CVS, it will be released with 1.21. > BTW, in my codes, I have overridden DBI.pm to establish the database > connection and return a DBH, I'd like to use that DBH for log4perl, how do I > go about doing it? There's no easy way to do that right now if you're using a configuration file, but if you attach the DBI appender via add_appender() in your code, you can pass in your $dbh to the constructor via new( dbh => $dbh). -- Mike Mike Schilli m...@pe... > > Thanks, > > David > > On Feb 11, 2009 4:49pm, "Kevin M. Goess" <cp...@go...> wrote: >> What are the rest of the contents of your testDbCon.pl script? >> >> >> >> And does this succeed? >> >> >> >> perl -MDBI -e 'DBI->connect(q/DBI:mysql:dbname=tmp;host=devserv/)' >> >> >> >> >> >> >> >> DavidZ wrote: >> >>> yes, I can connect to the database using mysql client, and tried to >> >>> connect without ";port=", still not working: >> >>> Log4perl: DBI appender failed to reconnect to database after 1 attempt >> >>> at ./test >> >>> s/testDbCon.pl line 38 >> >>> >> >>> Not sure why it's saying "reconnect". >> >>> thanks, >> >>> >> >>> David >> >>> >> >>> >> >>> On Tue, Feb 10, 2009 at 11:59 PM, Mike Schilli m...@pe... >> >>> m...@pe...>> wrote: >> >>> >> >>> On Tue, 10 Feb 2009, David Zhao wrote: >> >>> >> >>> = DBI:mysql:dbname=tmp;host=devserv;port= >> >>> log4perl.appender.DBAppender.username = user >> >>> log4perl.appender.DBAppender.password = 12345 >> >>> >> >>> >> >>> Can you connect to the database using the mysql client? Try >> >>> >> >>> mysql -uuser -p -h devserv tmp >> >>> >> >>> and when prompted for a password, type '12345'. If this works, the only >> >>> other suspicious item I noticed at first glance is the ";port=" part -- >> >>> try it without. >> >>> >> >> > |
