UCARP-based failover Bad Interface Name
Posted: Wed Mar 16, 2022 11:44 am
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
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