Latest percona-toolkit version 3.5.5-1 breaks pt-table-checksum
General
Escalation
General
Escalation
Description
Upgrading percona-toolkit to latest version 3.5.5-1.focal or 3.5.3-1.focal broke pt-table-checksums.
Command used:
dsns table:
Checksum errors show it can't connect to mysqld using the default socket path "/var/run/mysqld/mysqld.sock". Our socket path is different "/path/to/mysql/mysqld.sock" (masked path for security). It still runs the checksum on our tables and get results as shown below, but the can't connect errors cause a failed exit status.
PTDEBUG = 1 shows correct socket getting picked up. Previous versions up to and including 3.5.0-5.focal work fine, with no errors about default socket.
Thank you for the report. It is duplicate of https://jira.percona.com/browse/PT-2250, Please subscribe it to get notified whenever there is any updates. As a workaround please use previous version which were used before upgrading to latest one.
Upgrading percona-toolkit to latest version 3.5.5-1.focal or 3.5.3-1.focal broke pt-table-checksums.
Command used:
dsns table:
Checksum errors show it can't connect to mysqld using the default socket path "/var/run/mysqld/mysqld.sock". Our socket path is different "/path/to/mysql/mysqld.sock" (masked path for security). It still runs the checksum on our tables and get results as shown below, but the can't connect errors cause a failed exit status.
PTDEBUG = 1 shows correct socket getting picked up. Previous versions up to and including 3.5.0-5.focal work fine, with no errors about default socket.