OpenVPN Failed to Start

Gertjan

By now he knows that :

@jerelltk said in OpenVPN Failed to Start:

also unplugging power.

is a perfect way to break the file system, and this opens the door to all kind op issues.
The system will die / not being able to start up any more.
The issue would become far greater as 'openvpn not working'.

To test my words : use a not-important PC which has all data backed up.
Now,start the PC, count to 10.
Remove the power cord.
Repeat 10 times.

Your Windows /MAC/Linux/FreeBSD system won't boot anymore and you'll be seeing loads of obscure error messages (blue screens).

pfSense is not a light bulb.

To make things easy, and fast to resolve :

@jerelltk said in OpenVPN Failed to Start:

'/status_services.php: The command ‘/usr/local/sbin/openvpn —config ‘/var/etc/openvpn/client2/config.ovpn’ returned exit-code ‘1’, the output was ‘ld-elf.so.1:/lib/libnv.so.0: version FBSD_1.0 required by /usr/local/sbin/openvpn not defined’

this means : take the "re install pfSense"road.

And remember : use the Diagnostic => Halt GUI opinion to shut down the system.
Not the power cord.

n.lopyrev

@gertjan In my case, the netgate did not turn off. it works 100+ days. Today, several vpn servers restarted in 00:00 time. And we got the same error

/rc.newwanip: The command '/usr/local/sbin/openvpn --config '/var/etc/openvpn/server1/config.ovpn'' returned exit code '1', the output was 'ld-elf.so.1: /lib/libnv.so.0: version FBSD_1.0 required by /usr/local/sbin/openvpn not defined'

Gertjan

@n-lopyrev

pfSense version ?

[22.05-RELEASE][admin@pfSense.local.net]/root: ldd /usr/local/sbin/openvpn
/usr/local/sbin/openvpn:
        liblzo2.so.2 => /usr/local/lib/liblzo2.so.2 (0x800307000)
        liblz4.so.1 => /usr/local/lib/liblz4.so.1 (0x80033a000)
        libssl.so.111 => /usr/lib/libssl.so.111 (0x80036b000)
        libcrypto.so.111 => /lib/libcrypto.so.111 (0x800410000)
        libdl.so.1 => /usr/lib/libdl.so.1 (0x80070e000)
        libinotify.so.0 => /usr/local/lib/libinotify.so.0 (0x800712000)
        libnv.so.0 => /lib/libnv.so.0 (0x80071c000)
        libc.so.7 => /lib/libc.so.7 (0x800732000)
        libthr.so.3 => /lib/libthr.so.3 (0x800b0e000)

I didn't saw any updates, related to openvpn, for month now.
The pfSense openvpn client export package was updates a couple of time recently, but that didn't change anything for me.

Or are you using 2.6.0 CE ?

n.lopyrev

@gertjan I use Netgate 7100 with version OS

22.01-RELEASE (amd64)
built on Mon Feb 07 16:37:59 UTC 2022
FreeBSD 12.3-STABLE

n.lopyrev

@gertjan It is very strange. There are no encryption algorithms in the Data Encryption Algorithms. VPN: OpenVPN: Servers: Edit 2022-11-17 12-36-57.jpg

Gertjan

@n-lopyrev
Probably related.

Is there a reason you are not using the latest version ?

jerelltk

@n-lopyrev Yes, I decided to upgrade to the latest version because I noticed there was so many config files corrupted. I really don’t know how it happened. Now it’s working normal after the upgrade. I followed netgates instructions on upgrading, which I had to uninstall any packages then resinstall them after the upgrade.

thomas_br

Same error here. It's a Netgate 7100 appliance. +70 days uptime without any error.

/status_services.php: The command '/usr/local/sbin/openvpn --config '/var/etc/openvpn/server3/config.ovpn'' returned exit code '1', the output was 'ld-elf.so.1: /lib/libnv.so.0: version FBSD_1.0 required by /usr/local/sbin/openvpn not defined'

cpuch

Hello,

I'm having the same issue on Netgate 6100 with 21.05.2-RELEASE installed.

/status_services.php: The command '/usr/local/sbin/openvpn --config '/var/etc/openvpn/server3/config.ovpn'' returned exit code '1', the output was 'ld-elf.so.1: /lib/libnv.so.0: version FBSD_1.0 required by /usr/local/sbin/openvpn not defined'

Has anyone found a solution?

thomas_br

@cpuch Hi, I was using the same version here on 7100.

Solution: Backup and upgrade to 22.05-RELEASE.

Smooth upgrade here (removed ALL packages before upgrade and installed again after - refer to docs)

OpenVPN process is up and running now.

cpuch

@thomas-0 Thank you I'll try to upgrade.

crogerson

@thomas_br Really wish there was a real solution for this. Sure I need to upgrade my device, but I also have a problem right now that Netgate is aware of but has made no effort to resolve without further service impact.