| Bug #89123 | There is no local IP address matching the one configured for the local node | ||
|---|---|---|---|
| Submitted: | 5 Jan 2018 19:58 | Modified: | 13 Aug 2018 13:00 |
| Reporter: | MATTHEW MASSA | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Group Replication | Severity: | S3 (Non-critical) |
| Version: | 5.7.20, 5.7.21, 5.7.22 | OS: | MacOS (10.11.6 (El Capitan)) |
| Assigned to: | CPU Architecture: | Any | |
[5 Jan 2018 19:58]
MATTHEW MASSA
[8 Jan 2018 6:50]
MySQL Verification Team
Hello MATTHEW, Thank you for the report. Discussed internally with Dev and concluded that it is duplicate of Bug #86772 and per bug updates this has been fixed in upcoming versions and the following was added to the 5.7.21 / 8.0.4 changelog: Regardless of the number of virtual IPs configured on a machine, Group Replication could access only the first 12 addresses. Thanks, Umesh
[8 Jan 2018 14:38]
MATTHEW MASSA
Did you notice that the IP in question in my case is the only IP address on the interface? That doesn’t seem to fit the same conditions as the other bug...
[8 Jan 2018 16:50]
MATTHEW MASSA
For example, when I parse for IPv4 addresses on this server there are literally only 3: ifconfig | grep "inet " inet 127.0.0.1 netmask 0xff000000 inet 192.168.34.11 netmask 0xffffff00 broadcast 192.168.34.255 inet 10.100.6.11 netmask 0xffffff00 broadcast 10.100.6.255 That comes nowhere near the limit of 12 on an interface and these are on 3 different interfaces. Can you please check one more time?
[9 Jan 2018 4:17]
MySQL Verification Team
Thank you for the feedback. Please note that even if you feel that your issue is somewhat different but the fix for other issue also fixes this. I'll give it a try on both the versions(reported and fixed) and would let you know. In the meantime please provide conf files used in your environment to try at our end. Thank you for your interest in MySQL. Thanks, Umesh
[17 Jan 2018 11:27]
MySQL Verification Team
Also, 5.7.21 is released, may I request you to give it a try and confirm if you are still seeing the issue? I'm not seeing this issue at my end. Regards, Umesh
[28 Jan 2018 3:57]
MATTHEW MASSA
Gave it a shot tonight, unfortunately it looks like the new version won't run on El Capitan (10.11) only 10.12 and 10.13? Have a version that will run on 10.11 by any chance?
[12 Feb 2018 11:10]
Pratap Pradhan
Hi Umesh, I have tested the same using MySQL 5.7.21 but i am getting same issues. 2018-02-12T10:52:48.139181Z 11 [Note] Plugin group_replication reported: '[GCS] Translated 'mysql1' to x.x.x.x' 2018-02-12T10:52:48.139203Z 11 [ERROR] Plugin group_replication reported: '[GCS] There is no local IP address matching the one configured for the local node (mysql1:13306).' 2018-02-12T10:52:48.139216Z 11 [ERROR] Plugin group_replication reported: 'Unable to initialize the group communication engine' 2018-02-12T10:52:48.139221Z 11 [ERROR] Plugin group_replication reported: 'Error on group communication engine initialization' 2018-02-12T10:52:48.139225Z 11 [Note] Plugin group_replication reported: 'Requesting to leave the group despite of not being a member' 2018-02-12T10:52:48.139228Z 11 [ERROR] Plugin group_replication reported: 'Error calling group communication interfaces while trying to leave the group' 2018-02-12T10:57:49.227068Z 7 [Note] Aborted connection 7 to db: 'unconnected' user: 'root' host: 'mysql1' (Got timeout reading communication packets) Please update on same.
[20 Apr 2018 21:07]
David Ko
I'm also seeing this on a 5.7.21 instance installed on FreeBSD 11.
Sample log from mysql.err:
2018-04-20T10:09:09.828533Z 23 [Note] Plugin group_replication reported: '[GCS] Unable to probe network interface "igb0" for IP and netmask information. Skipping!'
2018-04-20T10:09:09.828572Z 23 [Note] Plugin group_replication reported: '[GCS] Unable to probe network interface "igb1" for IP and netmask information. Skipping!'
2018-04-20T10:09:09.828597Z 23 [ERROR] Plugin group_replication reported: '[GCS] There is no local IP address matching the one configured for the local node (xx.xx.xx.xx:33061).'
Network configuration:
igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether
hwaddr
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether
hwaddr
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
groups: lo
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether
inet xx.xx.xx.xx netmask 0xffffe000 broadcast xx.xx.xx.xx
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
groups: lagg
laggproto lacp lagghash l2,l3,l4
laggport: igb0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
laggport: igb1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
MySQL version:
# mysql --version
mysql Ver 14.14 Distrib 5.7.21, for FreeBSD11.1 (amd64) using EditLine wrapper
[24 Apr 2018 16:00]
Tiago Vale
Posted by developer: Hi everyone, Thank you for your interest in MySQL, and for your input on this bug in particular. I am just leaving this message here to assure you we are working on this. :-)
[30 May 2018 15:44]
MATTHEW MASSA
I was able to test this again with the latest release 5.7.22 (cluster 7.5.10 release) and we're still seeing it.
[13 Aug 2018 13:00]
David Moss
Posted by developer: Thank you for your feedback, this has been fixed in upcoming versions and the following was added to the 5.7.23 changelog: This bug was fixed by backporting the fix for bug#27376511.
