We had the same issue when we upgrade to galera 4, we used the value of wsrep_incoming_addresses in our monitoring scripts.
Work-around is set also 'wsrep_node_incoming_address' variable.

Yes, all of our monitoring applications suddenly got ruined after upgrading to Galera-4 due to wsrep_incoming_addresses just saying "AUTO" all the sudden. For example, here is what is getting passed to my wsrep_notify_cmd:

 --status joined

 --uuid 0db74c70-184d-11e8-81f3-2f1afb15c1c9

 --primary yes

 --index -1

 --members 528b829e-97dd-11ea-b29e-4b751ad2b256/node130/AUTO,df15aa3f-97de-11ea-af73-c728f9115f6b/node112/AUTO,f864ece2-97dd-11ea-b207-02205a497b45/node121/AUTO

Now I'm not even sure what "--index -1" means, but if that were more accurate, then at least it would be possible to determine what my own node_name was from this list of members. There really just needs to be some way to link the node_name to the IP Address for our monitoring application to function properly. Right now this seems impossible.

THANK YOU for the work-around of hacking wsrep_node_incoming_address to force it to show something more useful to prevent the monitor handler from crashing.

But I recommend please NEVER show "AUTO" for the "address" field! If "wsrep_node_incoming_address" is set to "AUTO" then it shall use "wsrep_node_address" or something more useful.

I noticed that "wsrep_node_incoming_address" is also set to "AUTO" in Galera-3, but everything worked much better somehow.

Hello, do you have any idea when it's will be fixed ?

it's really problematic for our monitoring too.

https://galeracluster.com/library/documentation/mysql-wsrep-options.html#wsrep-node-incoming-address

documentation say it too :

This parameter defines the IP address and port number at which the node should expect to receive client connections. It’s intended for integration with load balancers. For now, it’s otherwise unused by the node.

You can execute the SHOW VARIABLES statement with the LIKE operator as shown below to get the IP address and port setting of this parameter:

SHOW VARIABLES LIKE 'wsrep_node_incoming_address';

+-----------------------------+------------------+

| Variable_name               | Value            |

+-----------------------------+------------------+

| wsrep_node_incoming_address | 192.168.1.1:3306 |

+-----------------------------+------------------+

it's the only one way to know the others members of the cluster

and know when there is a SST who joiner

Careful. There are two parameters here, one is wsrep_incoming_address the other is wsrep_incoming_addresses.

The bug centers around the parameter wsrep_incoming_addresses, where instead reporting the IP addresses of the other acrive cluster nodes, it will report back as AUTO.

Why was this closed without any comment at all? This most certainly IS a bug, it is a feature regression, and it goes against the documented functionality of how this SHOULD work. Please re-open this ticket.

Although MDEV-28295 was filed as remove the dropped code, maybe it should actually be used.

I tested this on latest 10.3 and with following config

[mysqld.1]

wsrep-on=ON

wsrep-cluster-address=gcomm://

wsrep-provider=@ENV.WSREP_PROVIDER

binlog-format=ROW

wsrep_node_address=127.0.0.1

and I see following:

show variables like '%addres%';

Variable_name	Value

bind_address	127.0.0.1

wsrep_cluster_address	gcomm://

wsrep_node_address	127.0.0.1

wsrep_node_incoming_address	AUTO

wsrep_sst_receive_address	AUTO

darkain Can you provide your config and output from Galera 3 where it behaves differently i.e. gives real addresses on wsrep_node_incoming_address variable.

Same issue after upgrading to Mariadb10.5 / Galera 4:

MariaDB [(none)]> show status like 'wsrep_incoming_addresses';

+--------------------------+----------------+

| Variable_name            | Value          |

+--------------------------+----------------+

| wsrep_incoming_addresses | AUTO,AUTO,AUTO |

+--------------------------+----------------+

Why does this ticket keep on getting closed? This is STILL an unresolved regression, and I'm not sure what more feedback is needed. This is a pretty simple issue of "value reported IP addresses before, now only reports the word AUTO"

darkain Because we have not been able to find a version and config where wsrep_incoming_addresses would be something else than AUTO, changing it would mean external user change.

For our centos 6 with MariaDB 10.1 is was set to the ip addresses or node name automatically.
When we upgraded to centos 7 with 10.4 we need change the MariaDB configuration and set the wsrep_node_incoming_address in the mariadb configuration.

[galera]
wsrep_node_address = x.x.x.x
wsrep_node_incoming_address = x.x.x.x

1. mariadb
   Welcome to the MariaDB monitor. Commands end with ; or \g.
   Your MariaDB connection id is 1620710
   Server version: 10.4.12-MariaDB-log MariaDB Server

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> show status like 'wsrep_incoming_addresses';
-------------------------------------+

-------------------------------------+

-------------------------------------+
1 row in set (0.001 sec)

MariaDB [(none)]>

A lot of monitoring scripts use this value, so it'd be great if the old behaviour cloud be restored or it cloud be documented.

Hope this helps to reproduce this issue...

Jan Lindström, as others have said, go back and look at the behavior of MariaDB 10.1 and 10.2 using a version of Galera that matched those versions rather than a current version of Galera. This has been broken for quite some time and this ticket has been open since 2019, so yes, you need to find a MariaDB version older than the ticket. Only testing relatively "recent" versions of MariaDB of course has the change from IP addresses to "AUTO". There are examples in this bug report and version numbers listed in several of the comments.

Fully agree, I am facing this issue since an update from MariaDB10.3/Galera 3 to Mariadb10.5/Galera4. As staf wagemakers said, we also use this for monitoring purposes.

ramesh Can you test with 10.1 and 10.2.

jplindst 10.1 and 10.2 show the IP addresses in the wsrep_incoming_addresses status variable, even if you did not specify the IP address in the wsrep_node_incoming_address variable through the cnf file or the Galera startup command.

node1:root@localhost> select @@version;

+-----------------------+

| @@version             |

+-----------------------+

| 10.2.44-MariaDB-debug |

+-----------------------+

1 row in set (0.00 sec)

node1:root@localhost> 

Status variable

node1:root@localhost> SHOW GLOBAL STATUS LIKE 'wsrep_incoming_addresses';

+--------------------------+---------------------------------+

| Variable_name            | Value                           |

+--------------------------+---------------------------------+

| wsrep_incoming_addresses | 127.0.0.1:11531,127.0.0.1:10979 |

+--------------------------+---------------------------------+

1 row in set (0.00 sec)

node1:root@localhost>

10.1.49-opt>select @@version;

+-----------------+

| @@version       |

+-----------------+

| 10.1.49-MariaDB |

+-----------------+

1 row in set (0.00 sec)

10.1.49-opt>SHOW GLOBAL STATUS LIKE 'wsrep_incoming_addresses';

+--------------------------+---------------------------------+

| Variable_name            | Value                           |

+--------------------------+---------------------------------+

| wsrep_incoming_addresses | 127.0.0.1:10491,127.0.0.1:10913 |

+--------------------------+---------------------------------+

1 row in set (0.00 sec)

10.1.49-opt>

Because based on testing this is regression from 10.3 to 10.4, I will set this bug as a blocker.

Thx Jan Lindström !