[MDEV-8034] wsrep_node_address can't be ipv6 Created: 2015-04-22  Updated: 2016-02-17  Resolved: 2015-09-16

Status: Closed
Project: MariaDB Server
Component/s: Galera
Fix Version/s: 10.1.8

Type: Task Priority: Major
Reporter: Daniel Black Assignee: Nirbhay Choubey (Inactive)
Resolution: Fixed Votes: 0
Labels: galera, ipv6

Issue Links:
Problem/Incident
causes MDEV-8975 [PATCH] 10.1 Fails To Join Existing G... Closed
Relates
relates to MDEV-7676 Update site information on IPv6 suppo... Closed

 Description   

sql/wsrep_utils.cc:wsrep_guess_ip

const char* const colon_ptr = strchr(wsrep_node_address, ':');

Haven't checked wsrep_cluster_address or any of the sst scripts.



 Comments   
Comment by Nirbhay Choubey (Inactive) [ 2015-09-03 ]

https://github.com/codership/galera/issues/338

Comment by Nirbhay Choubey (Inactive) [ 2015-09-04 ]

http://lists.askmonty.org/pipermail/commits/2015-September/008301.html

Comment by Jan Lindström (Inactive) [ 2015-09-09 ]

Comments on email.

Comment by Nirbhay Choubey (Inactive) [ 2015-09-09 ]

jplindst I received no email. Have you sent it already?

Comment by Nirbhay Choubey (Inactive) [ 2015-09-16 ]

https://github.com/MariaDB/server/commit/bb52905432779d1648241baa5945c61617f2d58f

Comment by Daniel Black [ 2015-09-16 ]

thank you

Comment by Wido den Hollander [ 2016-02-17 ]

This is marked as resolved, but trying with MariaDB 10.1 this is still failing for me.

My configuration:

bind-address = *
wsrep_on=ON
wsrep_provider=/usr/lib/galera/libgalera_smm.so
wsrep_sst_method=rsync
wsrep_node_address="2a00:f10:121:XX:XX:a0ff:fe00:1bc7"

MariaDB fails to start and this is what I see in my logs:

Feb 17 15:49:12 ns011 mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Feb 17 15:49:12 ns011 mysqld_safe: WSREP: Running position recovery with --log_error='/var/lib/mysql/wsrep_recovery.Ovq0A1' --pid-file='/var/lib/mysql/ns011-recover.pid'
Feb 17 15:49:12 ns011 mysqld: 2016-02-17 15:49:12 139651198633920 [Note] /usr/sbin/mysqld (mysqld 10.1.11-MariaDB-1~trusty-log) starting as process 16377 ...
Feb 17 15:49:14 ns011 mysqld_safe: WSREP: Recovered position 6788b125-d581-11e5-b085-1fb01fb1ac24:0
Feb 17 15:49:15 ns011 mysqld: 2016-02-17 15:49:15 140428953855936 [Note] /usr/sbin/mysqld (mysqld 10.1.11-MariaDB-1~trusty-log) starting as process 16422 ...
Feb 17 15:49:15 ns011 mysqld: 2016-02-17 15:49:15 140428953855936 [Note] WSREP: Read nil XID from storage engines, skipping position init
Feb 17 15:49:15 ns011 mysqld: 2016-02-17 15:49:15 140428953855936 [Note] WSREP: wsrep_load(): loading provider library '/usr/lib/galera/libgalera_smm.so'
Feb 17 15:49:15 ns011 mysqld: 2016-02-17 15:49:15 140428953855936 [Note] WSREP: wsrep_load(): Galera 25.3.12(r3516) by Codership Oy <info@codership.com> loaded successfully.
Feb 17 15:49:15 ns011 mysqld: 2016-02-17 15:49:15 140428953855936 [Note] WSREP: CRC-32C: using hardware acceleration.
Feb 17 15:49:15 ns011 mysqld: 2016-02-17 15:49:15 140428953855936 [ERROR] WSREP: Can't parse port number from '1bc7': 22 (Invalid argument)
Feb 17 15:49:15 ns011 mysqld: #011 at galerautils/src/gu_uri.cpp:parse_authority():69
Feb 17 15:49:15 ns011 mysqld: 2016-02-17 15:49:15 140428953855936 [ERROR] WSREP: wsrep::init() failed: 7, must shutdown
Feb 17 15:49:15 ns011 mysqld: 2016-02-17 15:49:15 140428953855936 [ERROR] Aborting

So it has troubles parsing the IPv6 address.

I also tried:

wsrep_node_address="[2a00:f10:121:XX:XX:a0ff:fe00:1bc7]"

But that failed as well.

WSREP: Can't parse port number from '1bc7]': 22 (Invalid argument)

This is on a Ubuntu 14.04 system with 10.1.11+maria-1~trusty

Anything I'm missing here? The documentation doesn't show anything regarding IPv6.

Comment by Nirbhay Choubey (Inactive) [ 2016-02-17 ]

This is because of a limitation in galera library : https://github.com/codership/galera/issues/338

Comment by Wido den Hollander [ 2016-02-17 ]

Ok, but since this issues was marked as resolved I assumed the problem was resolved.

So currently it is not possible to run Galera clusters on IPv6-only?

Comment by Nirbhay Choubey (Inactive) [ 2016-02-17 ]

Ok, but since this issues was marked as resolved I assumed the problem was resolved.

There were some limitations in MariaDB code base too, now resolved.

So currently it is not possible to run Galera clusters on IPv6-only?

Some workarounds have been suggested in the last few comments : https://groups.google.com/forum/#!topic/codership-team/ERsd_-9YLr0

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