[MDEV-8731] IST bind address problem Created: 2015-09-02  Updated: 2016-08-18  Resolved: 2016-08-18

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.0.19-galera
Fix Version/s: 5.5.51-galera

Type: Bug Priority: Major
Reporter: Zhani Baramidze Assignee: Nirbhay Choubey (Inactive)
Resolution: Fixed Votes: 1
Labels: None


 Description   

I'm trying to implement mariadb galera cluster behind docker, and I have following problem. IST tries to listen to ip suppolied by wsrep_node_address, which is "external" ip:

[Note] WSREP: Prepared IST receiver, listening at: tcp://192.168.1.211:4568

but it fails, because it cannot bind listening socket to 192.168.1.211, because it's external:

[Warning] WSREP: 0.0 (h2): State transfer to 1.0 (h1) failed: -111 (Connection refused)

so I changed ist.recv_addr to 0.0.0.0, and it starts listening correctly but then other peer tries to connect to 0.0.0.0:

150902  9:51:18 [ERROR] WSREP: IST failed: IST sender, failed to connect 'tcp://0.0.0.0:4568': Connection refused: 111 (Connection refused)
 
	 at galera/src/ist.cpp:Sender():576
 
 

how is this possible to make IST work under NAT?

 Comments   
Comment by sirotopr [ 2015-10-17 ]

+1

This is a major bug. Should get some attention.
It was reported on Galera's GitHub an year ago: https://github.com/codership/galera/issues/105

Comment by Kristian Klausen [ 2016-03-15 ]

This has been resolved upstream.
https://github.com/codership/galera/pull/372
Do we wait for a new Galera release, or do we patch the current version?

Comment by Nirbhay Choubey (Inactive) [ 2016-03-15 ]

This patch was not part of 25.3.15, released by Codership yesterday. So, we have to wait for 25.3.16.

Comment by Nirbhay Choubey (Inactive) [ 2016-08-18 ]

Fixed in Galera 25.3.17.

Generated at Thu Feb 08 07:29:21 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.