Details
-
Type:
New Feature
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Not a Bug
-
Affects Version/s: 2.5.5
-
Fix Version/s: N/A
-
Component/s: N/A
-
Labels:None
-
Environment:Debian 10.7, keepalived vip
Description
Hello!
When using maxscale with keepalived virtual ip there is an error on a backup node:
Starting a total of 1 services... |
Failed to bind on '10.0.1.254:4006': 99, Cannot assign requested address |
Failed to bind on '10.0.1.254:4006': 99, Cannot assign requested address |
Failed to bind on '10.0.1.254:4006': 99, Cannot assign requested address |
Failed to bind on '10.0.1.254:4006': 99, Cannot assign requested address |
(Read-Write-Listener) One or more workers failed to listen on '[10.0.1.254]:4006'. |
Service 'Read-Write-Service' started (1/1) |
Failed to start service 'Read-Write-Service'. |
Failed to start all MaxScale services.
|
The error appears because 10.0.1.254 is virtual ip and it assigned on master node. When fail on master node occurs this virtual IP must migrate to backup node. There is a workaround don't bind maxscale to particular ip and use bind 0.0.0.0 but it bad for security reasons.
Can we change bind behavior and allow to bind on non-existent ip-addresses on the backup host?