NordVPN today update Version 3.12.0 not work in SysVinit [Solved]

[asqwerth]

By the way, I get the same "sock" error message in Fedora (systemd) after an update of nordvpn via their rpm repos.

I do have to reinstall the package whenever that happens and re-enable the service with the appropriate systemctl command, then reboot.

So it may not be merely a sysv thing but a nordvpn thing.

[fehlix]

By the way, I get the same "sock" error message in Fedora (systemd) after an update of nordvpn via their rpm repos.

I do have to reinstall the package whenever that happens and re-enable the service with the appropriate systemctl command, then reboot.

So it may not be merely a sysv thing but a nordvpn thing.

That, was my suspicion too, b/c after a service nordvpn restart, the socket is available and it offers me to connect. Also the PID error is some typical type of not properly setup "service"

[asqwerth]

I've booted into my mx21 beta and note that my working nordvpn was at ver 3.11. There is now an update to 3.12. I'll install the update, reboot and see what happens.

[UPDATED]
Yep, after upgrade, I rebooted and got the same "whoops sock" message as the other posters when I tried to connect.

Per @fehlix 's instructions, I started the service again (sysV). I did not uninstall or reinstall the nordvpn package at all, just restarted service.

I got the apparent error message as the other poster:

Code: Select all

$ sudo service nordvpn restart
[sudo] password for tuaz: 
Restarting /usr/sbin/nordvpnd: nordvpnstart-stop-daemon: warning: failed to kill 1892: No such process

But a subsequent

Code: Select all

nordvpn c

does successfully connect the vpn.

[UPDATE 2]

After reboot, you have to again restart the service otherwise you get the whoops sock message. So

Code: Select all

sudo service xxx restart 

is equivalent to

Code: Select all

sudo systemctl start xxx

, which is just a one-off start command.

WHat is the sysV equivalent of

Code: Select all

sudo systemctl enable xxx

, which enables a service on start up?

Google searches show the command is

Code: Select all

sudo chkconfig xxx on

but no such command is found in MX21.

[Cristobal]

Indeed, after restarting twice, it eventually connected.

Code: Select all

$ sudo service nordvpn restart
[....] Restarting /usr/sbin/nordvpnd: nordvpnstart-stop-daemon: warning: failed to kill 2300: No such process
. ok 

[bvliegen]

Same problem here. Got the whoops etc. message. After restarting with systemd nordvpn works again.

[asqwerth]

Indeed, after restarting twice, it eventually connected.

Code: Select all

$ sudo service nordvpn restart
[....] Restarting /usr/sbin/nordvpnd: nordvpnstart-stop-daemon: warning: failed to kill 2300: No such process
. ok 

That message had no effect on the restart command, in the sense that after I ran the restart command ONCE, the first

Code: Select all

nordvpn c

after that got nordvpn up and running.

The only issue now I have is getting the service to be enabled all the time on bootup so I don't have to keep starting the service.

[fehlix]

Indeed, after restarting twice, it eventually connected.

Code: Select all

$ sudo service nordvpn restart
[....] Restarting /usr/sbin/nordvpnd: nordvpnstart-stop-daemon: warning: failed to kill 2300: No such process
. ok 

That message had no effect on the restart command, in the sense that after I ran the restart command ONCE, the first

Code: Select all

nordvpn c

after that got nordvpn up and running.

The only issue now I have is getting the service to be enabled all the time on bootup so I don't have to keep starting the service.

OK. It might be just a timing / dbus issue.
Perhaps only a timing issue:
This might fix it by adding a 3 sec delay into start :

Code: Select all

sudo sed  -i '/ start)/a\    sleep 3' /etc/init.d/nordvpn

[venik212]

I had a similar problem with 3.12, and following the suggestion of the Nordvpn support, I removed all traces of the non-functioning version 3.12, and installed version 3.10, which works, but is invisible to the MX Linux package installer or Synaptic... ;-(

[fehlix]

I had a similar problem with 3.12, and following the suggestion of the Nordvpn support, I removed all traces of the non-functioning version 3.12, and installed version 3.10, which works, but is invisible to the MX Linux package installer or Synaptic... ;-(

Actually you could downgrade to a lower version number within Synaptic.

* Quick filter: nordvpn
* Select nordvpn and press Ctrl+E ( Menu: Package -> Force version )

NordVPN-Package-force-version.png

* and select the lower version 3.10

NordVPN-Force-version.png

* After downgrade do lock/pin the version to the one installed:

NordVPN-Lock-version.png

Note: "MX Updater" takes into account the pinned/hold version specified by Synaptic and does not perform an upgrade.
Running "apt full-upgrade" manually on the command line would ignore Synaptic's pinned version and would upgrade.

++EDIT+++
Actually after having upgraded from 3.10 to 3.12
and manually added the mentioned delay this way
booted in either SysVinit or systemd:
First stop it:

Code: Select all

sudo service nordvpn stop

Add a delay:

Code: Select all

sudo sed  -i '/ start)/a\    sleep 2' /etc/init.d/nordvpn

Note: In systemd it will use the shown SysVInit script (!) through MX Linux used systemd-shim helper.
And start again:

Code: Select all

sudo service nordvpn start

Rebooting into SysVinit or systemd always made nordvpn running.

[asqwerth]

@fehlix

I added the delay to the init script following all your instructions, then rebooted. I still get the whoops sock error.

I can still restart service to make it work but it doesn't work OOTB upon reboot.