pt-table-checksum error at runtime DBD::mysql::dr::imp_data_size

Bug #1308299 reported by Peter Sylvester on 2014-04-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit

Bug Description

Command used:
pt-table-checksum --databases=<db here> --user=psylvester --password=<password here>

Had to create DBD::mysql::dr::imp_data_size unexpectedly at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/ 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/ line 1190.
04-15T21:28:56 Undefined subroutine &DBD::mysql::db::_login called at /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/DBD/ line 149.

pt-table-checksum 2.2.7

I ran the installation seperately on a pair of VMs and did not have the issue listed above. This only appears to be happening on our production server which is running CentOS 5.10

tags: added: pt-table-checksum
Muhammad Irfan (muhammad-irfan) wrote :

I can't reproduce this issue. To me it's more like an issue with perl-DBD-MySQL
Probably wrong rpm installed or not installed accordingly 32/64 bit architecture for perl-DBD-MySQL.
How did you installed perl dbd-mysql module via yum or rpm or manually ? Can you try to remove/install dbd-mysql and check if it works.

 [root@centos59]# /root/downloads/percona-toolkit-2.2.7/bin/pt-table-checksum --version
pt-table-checksum 2.2.7
[root@centos59]# /root/downloads/percona-toolkit-2.2.7/bin/pt-table-checksum --databases=test --user=msandbox --password=msandbox --socket=/tmp/mysql_sandbox20484.sock
Cannot connect to h=,p=...,u=msandbox
Diffs cannot be detected because no slaves were found. Please read the --recursion-method documentation for information.
08-28T12:16:49 0 0 4079 4 0 0.240 test.City
08-28T12:16:49 0 0 239 1 0 0.104 test.Country
08-28T12:16:49 0 0 984 1 0 0.009 test.CountryLanguage
08-28T12:16:49 0 0 9738 1 0 0.080 test.flaggedrevs
08-28T12:16:49 0 0 2 1 0 0.043 test.messages
08-28T12:16:49 0 0 0 1 0 0.013 test.messages_innodb

Changed in percona-toolkit:
status: New → Invalid
Changed in percona-toolkit:
status: Invalid → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for Percona Toolkit because there has been no activity for 60 days.]

Changed in percona-toolkit:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers