pt-table-checksum --recursion-method=cluster tries to use the galera port to connect to

Reported by Kenny Gryp on 2013-09-04
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona Toolkit
High
Daniel Nichter

Bug Description

[root@svrentpsql01 bin]# ./pt-table-checksum --recursion-method cluster -u percona -ptempaccess
Cannot connect to P=4567,h=172.29.126.138,p=...,u=percona, discovered through SHOW STATUS LIKE 'wsrep\_incoming\_addresses': DBI connect(';host=172.29.126.138;port=4567;mysql_read_default_group=client','percona',...) failed: Wrong or unknown protocol at ./pt-table-checksum line 1586

Cannot connect to P=4567,h=172.29.126.137,p=...,u=percona, discovered through SHOW STATUS LIKE 'wsrep\_incoming\_addresses': DBI connect(';host=172.29.126.137;port=4567;mysql_read_default_group=client','percona',...) failed: Wrong or unknown protocol at ./pt-table-checksum line 1586

Cannot connect to P=4567,h=172.29.126.140,p=...,u=percona, discovered through SHOW STATUS LIKE 'wsrep\_incoming\_addresses': DBI connect(';host=172.29.126.140;port=4567;mysql_read_default_group=client','percona',...) failed: Wrong or unknown protocol at ./pt-table-checksum line 1586

Use of uninitialized value in string ne at ./pt-table-checksum line 9206.

Why does mysql want to connect to port 4567? This is a galera connection port and should not be used to connect to mysql.

Kenny Gryp (gryp) wrote :

The tool then also quits as reported in bug 1210537

tags: added: i35005
tags: added: crash percona-35005 pt-table-checksum pxc
removed: i35005
Changed in percona-toolkit:
assignee: nobody → Daniel Nichter (daniel-nichter)
importance: Undecided → High
status: New → Confirmed
Changed in percona-toolkit:
milestone: none → 2.2.5
tags: added: slave-recursion
Daniel Nichter (daniel-nichter) wrote :

"Use of uninitialized value in string ne at ./pt-table-checksum line 9206." was fixed in bug 1210537.

Changed in percona-toolkit:
status: Confirmed → In Progress
Daniel Nichter (daniel-nichter) wrote :

Kenny,

What does SHOW STATUS LIKE 'wsrep\_incoming\_addresses' return?

Daniel Nichter (daniel-nichter) wrote :

And do you have PTDEBUG output? And what version of PXC?

tags: removed: crash
Kenny Gryp (gryp) wrote :

PXC version was: '5.5.30-log Percona XtraDB Cluster (GPL), wsrep_23.7.4.r3843'

Jeroen Moors (jeroen-moors) wrote :

mysql> SHOW STATUS LIKE 'wsrep\_incoming\_addresses';
+--------------------------+-------------------------------------------------------------+
| Variable_name | Value |
+--------------------------+-------------------------------------------------------------+
| wsrep_incoming_addresses | 172.29.126.138:4567,172.29.126.137:4567,172.29.126.140:4567 |
+--------------------------+-------------------------------------------------------------+
1 row in set (0.00 sec)

Daniel Nichter (daniel-nichter) wrote :

wsrep_incoming_address "Shows the comma-separated list of incoming node addresses in the cluster." What exactly does this mean? Of course the IP is for the remote, i.e. incoming node, but is the port also the remote's port or is it the local port? Plus, like you said, it's for Galera so nodes shouldn't be using it, so why is wsrep_incoming_address showing it here?

Changed in percona-toolkit:
milestone: 2.2.5 → none
Kenny Gryp (gryp) wrote :

This is very odd Daniel, Some other PXC installations I checked did not have :4567, but :3306 in there.
Maybe it's a PXC/Galera bug?

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

Other bug subscribers