-
Type:
Bug
-
Status: Done
-
Priority:
Low
-
Resolution: Invalid
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Packaging
-
Labels:
-
Launchpad URL:
**Reported in Launchpad by Keith Murphy last update 30-10-2013 23:48:16
We recently upgraded from Percona-Server 5.1 to 5.5. I noticed today that pt-deadlock-logger was not running. We have it deployed/daemonized to run every 30 seconds. On every server it was not running. Trying to restart it produce the following:
- pt-deadlock-logger --create-dest-table --dest D=admin,t=deadlocks h=127.0.0.1
Had to create DBD::mysql::dr::imp_data_size unexpectedly at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/DBI.pm line 1190.
Had to create DBD::mysql::db::imp_data_size unexpectedly at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/DBI.pm line 1190.
Undefined subroutine &DBD::mysql::db::_login called at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/DBD/mysql.pm line 140.
#
This error seemed to indicate that authentication was failing however the users on the systems didn't change.
After a bit of thought i realized that previously I had the shared-compat package installed with Percona Server 5.1 and only installed the shared package with 5.5. Installing the shared-package resolved the issue.
Apparently something in the shared-compatability package (a libmysqlclient i assume) is required for pt-deadlock-logger. If this is true, then the shared-compatability package should be a requirement for installation of the toolkit.