Systemctl does not survive reboot

Hello,

The “systemctl” commands seem to do not survive the reboot on Fedora-31-based VMs. E.g., “sudo systemctl enable --now nordvpnd.service” activates the vpn daemon, but on reboot nothing happens. How to fix this?

I would expect that using this command, the vpn would start automatically on reboot. But on reboots it prints “vpn daemon is not active” (or something like that).

Thank you.

The “systemctl” commands seem to do not survive the reboot on Fedora-31-based VMs. E.g., “sudo systemctl enable --now nordvpnd.service” activates the vpn daemon, but on reboot nothing happens. How to fix this?

I assume you are running this command in an AppVM, not a template? The
AppVM will lose it’s root filesystem on reboot, meaning that all systemd
configuration will be reverted to that of the template.

AppVM specific services are started in /rw/config/rc.local. You should
be able to add a line there with systemctl start nordvpnd.service and
have it start automatically.

1 Like