Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Not a Bug
-
6.4.4
-
None
-
MXS-SPRINT-173, MXS-SPRINT-174
Description
Maxscale 6.4.4 has a bug where in if Maxscale service starts (or restarts) after Proxy protocol has been set on Xpand (6.1_beta2), its not able to discover xpand nodes. This works fine with version 22.08.3.
These are repro steps:
1. Enable proxy protocol on xpand (i.e. set global proxy_protocol_networks= maxscale ip)
2. Enable proxy protocol on Maxscale (i.e. set proxy_protocol=on in config)
3. Start maxscale. It's not able to discover xpand nodes.
Another way to repro this is to restart maxscale anytime after proxy_protocol is enabled on xpand and maxscale.
Logs:
2022-12-09 01:09:49 error : [xpandmon] Backend-Monitor: Could either not ping or create connection to karma013.colo.sproutsys.com:3306: Lost connection to server at 'reading authorization packet', system error: 110
|
2022-12-09 01:09:49 notice : [xpandmon] Attempting to find a Xpand bootstrap node from one of the nodes used during the previous run of MaxScale.
|
2022-12-09 01:09:49 notice : [xpandmon] Trying to find out cluster nodes from 10.2.15.13:3306.
|
To get out of this situation, you do following on xpand:
MySQL [(none)]> set global proxy_protocol_networks='';
|
Query OK, 0 rows affected (0.06 sec)
|
Restart maxscale
MySQL [(none)]> set global proxy_protocol_networks='10.2.13.172/32';
|
Query OK, 0 rows affected (0.07 sec)
|
Maxctrl does not work either:
[root@karma153 ~]# maxctrl list servers
|
Error: Could not connect to MaxScale
|
[root@karma153 ~]# maxctrl show servers
|
Error: Could not connect to MaxScale
|