Howzit Ken
Erik is correct. This doesn’t look like a bug, but a misconfiguration. Looking at your snipped, this is where your problem starts.
TCP/UDP: Socket bind failed on local address [AF_INET][undef]:1194: Address alre ady in use (errno=98)
Everything thereafter is a direct result of not being able to establish a connection correctly.
By default OVPN runs on UDP/1194. This is also the port used for Roadwarriors.
I have a few sites with single or multiple N2N OpenVPN configurations.
The N2N will need to have additional ports assigned to it, you cannot use UDP/1194, this will cause issues. Assign anything you like, recommend is to stick with UDP it’s faster, but there is nothing that can stop you from going TCP if you feel you must.
Use a port not in use by anything else on your networks (server and client side). Don’t use UDP/500 or UDP/4500 if you are also running IPSEC (default ports), use TCP/500 or TCP/4500 instead if you want to keep the numbers.
Better yet, check what ports are in use by which service and where it’s pointing to.
lsof -i -P -n | grep LISTEN
Should let you know what is open currently.
Also remember that both VPN sides cannot have the same IP range. If side A is 192.168.27.0/24 then side B needs to be something else, i.e. 192.168.28.0/24.
I hope this helps you along. Cheers