No useful error messages if an SSL-disabled node tries to join an SSL-enabled cluster
General
Escalation
General
Escalation
Description
Repro:
Start up node1 (bootstrapped), with pxc-encrypt-cluster-traffic=ON
Start up node2 with pxc-encrypt-cluster-traffic=OFF
Result:
On the joiner, we see a series of "no messages seen" and then it times out and aborts. Nothing appears on the donor side.
2020-03-06T02:08:45.443104Z 0[Note][MY-000000][Galera](57da8f76,'tcp://192.168.86.137:5230') connection topeer00000000withaddr tcp://192.168.86.137:5130 timed out, no messages seen in PT3S (gmcast.peer_timeout)2020-03-06T02:08:49.445572Z 0[Note][MY-000000][Galera](57da8f76,'tcp://192.168.86.137:5230') connection topeer00000000withaddr tcp://192.168.86.137:5130 timed out, no messages seen in PT3S (gmcast.peer_timeout)2020-03-06T02:08:49.946109Z 0[Note][MY-000000][Galera] PC protocol downgrade 1->02020-03-06T02:08:49.946320Z 0[Note][MY-000000][Galera]Current view of cluster as seen by this node
view ((empty))2020-03-06T02:08:49.946693Z 0[ERROR][MY-000000][Galera] failed toopengcomm backend connection:110: failed toreach primary view (pc.wait_prim_timeout):110(Connection timed out) at gcomm/src/pc.cpp:connect():1592020-03-06T02:08:49.946720Z 0[ERROR][MY-000000][Galera] gcs/src/gcs_core.cpp:gcs_core_open():220:Failedtoopenbackend connection:-110(Connection timed out)2020-03-06T02:08:49.946800Z 0[ERROR][MY-000000][Galera] gcs/src/gcs.cpp:gcs_open():1694:Failedtoopenchannel'my_cluster' at 'gcomm://192.168.86.137:5130':-110(Connection timed out)2020-03-06T02:08:49.946817Z 0[ERROR][MY-000000][Galera] gcs connect failed:Connection timed out
2020-03-06T02:08:49.946832Z 0[ERROR][MY-000000][WSREP]Provider/Node(gcomm://192.168.86.137:5130) failed toestablish connection withcluster(reason:7)2020-03-06T02:08:49.946848Z 0[ERROR][MY-010119][Server]Aborting2
We should record all connection attempts, at the very least on the donor side.
Environment
None
Activity
Show:
Julia Vural
March 4, 2025 at 9:27 PM
It appears that this issue is no longer being worked on, so we are closing it for housekeeping purposes. If you believe the issue still exists, please open a new ticket after confirming it's present in the latest release.
Tyler Duzan
March 16, 2020 at 7:32 PM
This is being removed as a blocker for PXC 8.0 GA as part of the triage process. We believe that this issue can be resolved in a point release post-GA. In the interim, documentation can suffice to cover this case.
Repro:
Start up node1 (bootstrapped), with pxc-encrypt-cluster-traffic=ON
Start up node2 with pxc-encrypt-cluster-traffic=OFF
Result:
On the joiner, we see a series of "no messages seen" and then it times out and aborts. Nothing appears on the donor side.
2020-03-06T02:08:45.443104Z 0 [Note] [MY-000000] [Galera] (57da8f76, 'tcp://192.168.86.137:5230') connection to peer 00000000 with addr tcp://192.168.86.137:5130 timed out, no messages seen in PT3S (gmcast.peer_timeout) 2020-03-06T02:08:49.445572Z 0 [Note] [MY-000000] [Galera] (57da8f76, 'tcp://192.168.86.137:5230') connection to peer 00000000 with addr tcp://192.168.86.137:5130 timed out, no messages seen in PT3S (gmcast.peer_timeout) 2020-03-06T02:08:49.946109Z 0 [Note] [MY-000000] [Galera] PC protocol downgrade 1 -> 0 2020-03-06T02:08:49.946320Z 0 [Note] [MY-000000] [Galera] Current view of cluster as seen by this node view ((empty)) 2020-03-06T02:08:49.946693Z 0 [ERROR] [MY-000000] [Galera] failed to open gcomm backend connection: 110: failed to reach primary view (pc.wait_prim_timeout): 110 (Connection timed out) at gcomm/src/pc.cpp:connect():159 2020-03-06T02:08:49.946720Z 0 [ERROR] [MY-000000] [Galera] gcs/src/gcs_core.cpp:gcs_core_open():220: Failed to open backend connection: -110 (Connection timed out) 2020-03-06T02:08:49.946800Z 0 [ERROR] [MY-000000] [Galera] gcs/src/gcs.cpp:gcs_open():1694: Failed to open channel 'my_cluster' at 'gcomm://192.168.86.137:5130': -110 (Connection timed out) 2020-03-06T02:08:49.946817Z 0 [ERROR] [MY-000000] [Galera] gcs connect failed: Connection timed out 2020-03-06T02:08:49.946832Z 0 [ERROR] [MY-000000] [WSREP] Provider/Node (gcomm://192.168.86.137:5130) failed to establish connection with cluster (reason: 7) 2020-03-06T02:08:49.946848Z 0 [ERROR] [MY-010119] [Server] Aborting 2
We should record all connection attempts, at the very least on the donor side.