Page 1 of 1

UCARP-based failover Bad Interface Name

Posted: Wed Mar 16, 2022 11:44 am
by hopa
Hi,

I try to evaluate the for future use before switching from fixed to subscriptions, so i followed this instructions https://openvpn.net/vpn-server-resource ... over-mode/
First Node runs as KVM, second node on a Bare-metal server.

On Testing Failover I got the following error on the secondary node:
Server Agent is inactive due to the following errors: {'errors': {'cs.https.ip_address': [('error', "LOCAL_ADDR enp1s0 : bad local address name or interface is not up; must be 'all', 'localhost', a local IP address, or an interface name: r: [Error: service failed to start due to unresolved dependencies: {'user'}.]....."}, 'last_restarted''}

The baremetal hasn't any interface enp1s0, it's interface name is enp3s4f0. On first node interface name is enp1s0.

Thanks in advance,
Pat

Re: UCARP-based failover Bad Interface Name

Posted: Wed Mar 16, 2022 11:57 am
by openvpn_inc
Hello hopa,

I'd suggest changing it to 'whateveryourinterfacenameis' and see if that helps.
cd /usr/local/openvpn_as/scripts/
./sacli --key "cs.https.ip_address" --value "whateveryourinterfacenameis" configput
./sacli start

Kind regards,
Johan