[MDEV-14329] (draft) galera fails to join default port on the same host Created: 2017-11-08  Updated: 2018-02-05  Resolved: 2018-02-05

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.2
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Andrii Nikitin (Inactive) Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-14328 (draft) galera ignores bind-address a... Closed

 Description   

The same works if donor's default port 4567 is explicitly mention in wsrep_cluster_address on joiner

2017-11-08 16:10:57 140296941360640 [Note] WSREP: (05e1dbb0, 'tcp://0.0.0.0:4574') listening at tcp://0.0.0.0:4574
2017-11-08 16:10:57 140296941360640 [Note] WSREP: (05e1dbb0, 'tcp://0.0.0.0:4574') multicast: , ttl: 1
2017-11-08 16:10:57 140296941360640 [Note] WSREP: EVS version 0
2017-11-08 16:10:57 140296941360640 [Note] WSREP: gcomm: connecting to group '192.168.1.183_11', peer '192.168.1.183:'
2017-11-08 16:10:57 140296941360640 [Note] WSREP: (05e1dbb0, 'tcp://0.0.0.0:4574') connection established to 05e1dbb0 tcp://192.168.1.183:4574
2017-11-08 16:10:57 140296941360640 [Warning] WSREP: (05e1dbb0, 'tcp://0.0.0.0:4574') address 'tcp://192.168.1.183:4574' points to own listening address, blacklisting
2017-11-08 16:11:00 140296941360640 [Note] WSREP: (05e1dbb0, 'tcp://0.0.0.0:4574') connection to peer 05e1dbb0 with addr tcp://192.168.1.183:4574 timed out, no messages seen in PT3S
2017-11-08 16:11:00 140296941360640 [Warning] WSREP: no nodes coming from prim view, prim not possible
2017-11-08 16:11:00 140296941360640 [Note] WSREP: view(view_id(NON_PRIM,05e1dbb0,1) memb {
        05e1dbb0,0
} joined {
} left {
} partitioned {
})
2017-11-08 16:11:01 140296941360640 [Warning] WSREP: last inactive check more than PT1.5S ago (PT3.50076S), skipping check
2017-11-08 16:11:30 140296941360640 [Note] WSREP: view((empty))
2017-11-08 16:11:30 140296941360640 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view: 110 (Connection timed out)
         at gcomm/src/pc.cpp:connect():158
2017-11-08 16:11:30 140296941360640 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():208: Failed to open backend connection: -110 (Connection timed out)
2017-11-08 16:11:30 140296941360640 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1404: Failed to open channel '192.168.1.183_11' at 'gcomm://192.168.1.183': -110 (Connection timed out)
2017-11-08 16:11:30 140296941360640 [ERROR] WSREP: gcs connect failed: Connection timed out
2017-11-08 16:11:30 140296941360640 [ERROR] WSREP: wsrep::connect(gcomm://192.168.1.183) failed: 7
2017-11-08 16:11:30 140296941360640 [ERROR] Aborting



 Comments   
Comment by Elena Stepanova [ 2018-01-27 ]

winstone, could you please quickly check if you can reproduce it? If not, no need to spend much time.

Comment by Zdravelina Sokolovska (Inactive) [ 2018-01-29 ]

it's missing /my.cnf.d/server.cnf configuration, firewall configuration and OS info

Generated at Thu Feb 08 08:12:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.