pt-table-sync cannot connected slave

Bug #870510 reported by weixiao
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Won't Fix
Undecided
Unassigned

Bug Description

Hi :

I am trouble when i use pt-table-sync tool

i run command:
   pt-table-sync --databases=test --user=root --socket=/data/mysqldata3306/sock/mysql.sock --print --sync-to-master --replicate test.checksum localhost

result :
The server specified as a master has no connected slaves at /usr/bin/pt-table-sync line 6004

Replicat is running , and it is nomal .I try to remove --socket from DSN,still have problem

Please reslove it ,thanks

weixiao (ben-xiaowei)
summary: - pt-table-sync disappear
+ pt-table-sync cannot connected slave
security vulnerability: yes → no
visibility: private → public
tags: added: pt-table-sync slave-recursion
Revision history for this message
Brian Fraser (fraserbn) wrote :

Hey weixiao.

Thank you for your bug report; Are you still having this issue? If so, could you run the tool with PTDEBUG=1 and post the output here?

Revision history for this message
Daniel Nichter (daniel-nichter) wrote :

Socket files break the process of finding slaves. You're not using --socket any longer, but does a .my.cnf file specify a socket file?

Changed in percona-toolkit:
status: New → Triaged
Revision history for this message
Baron Schwartz (baron-xaprb) wrote :

I am marking this invalid because there hasn't been a response, but I will file a new bug report with the issue we believe to be at play.

Changed in percona-toolkit:
status: Triaged → Invalid
Revision history for this message
Baron Schwartz (baron-xaprb) wrote :

See also bug 1010031.

Revision history for this message
Baron Schwartz (baron-xaprb) wrote :

It seems that "Invalid" is still an Open status in Launchpad. I'll WontFix this so it is closed.

Changed in percona-toolkit:
status: Invalid → Won't Fix
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-880

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.