-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to add VIP #46
Comments
vip_ipv4 in the config is meant to be the IP shared between two seesaws in a HA cluster. The software expects to add and manage the IP as determined by the HA process. It looks like you already have that IP address on the device, which may be what the engine is complaining about. Try removing the IP from ens4 and trying again. |
Doesn't seem to change the outcome.
It complains if there's no dummy interface configured but it doesn't seem to have any impact. Does the load balanced service need to be running? |
Have you fixed the above error yet? I also got the same error |
Unable to start seesaw_engine and checking
/var/log/seesaw/seesaw_engine.INFO
, I get the errorF0102 23:51:23.323436 2584 vserver.go:1359] server.br11@kvm.test: failed to add VIP 10.240.11.65: IP run "addr add 10.240.11.65/24 brd 10.240.11.255 dev ens4": exit status 2
seesaw.cfg is:
ip addr show
:systemctl status seesaw_watchdog
:Is there any guides with regards to interface configuration.
The text was updated successfully, but these errors were encountered: