Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Okay, do you happen to know a solution to my issue? It seems like the same issue I was having but apparently I cannot use this solution. When I reboot my Pi, OpenVPN is started but I cannot connect to it. I reload the service and it works perfect fine. It looks like it has something with the boot sequence of how the services are loaded. Could you help me? Thanks.
I simply edit my openvpn@.service and added 'After=ntp.service' and now OpenVPN is loading on every boot.
These are indeed instructions for the systemd way of system initialization. First, check if your Pi uses this - it's sufficient to just type "systemctl" with no parameters. If the systemctl program exists and dumps out a list of services, you are in business. If not, you need different instructions.
Assuming systemd, you will have to find a file named openvps@.service, probably under /etc/systemd/system or elsewhere under /etc/systemd. Use a text editor to open this file and add the line After=ntp.service, probably in the [Unit] section (I am not so good at systemd yet).
This line simply means that the openvps service will be started when the network time service is running.
Last edited by berndbausch; 11-09-2015 at 02:10 PM.
These are indeed instructions for the systemd way of system initialization. First, check if your Pi uses this - it's sufficient to just type "systemctl" with no parameters. If the systemctl program exists and dumps out a list of services, you are in business. If not, you need different instructions.
Assuming systemd, you will have to find a file named openvps@.service, probably under /etc/systemd/system or elsewhere under /etc/systemd. Use a text editor to open this file and add the line After=ntp.service, probably in the [Unit] section (I am not so good at systemd yet).
This line simply means that the openvps service will be started when the network time service is running.
Is it openvps@.service OR openvpn@.service?
Last edited by joshuambenhase; 11-09-2015 at 02:17 PM.
I think you copy /lib/systemd/system/openvpn@.service to /etc/systemd/system, then apply the above changes.
The files under /etc/systemd are for sysadmin modification, the ones under /lib should be left alone. /etc files override /lib files.
Don't listen to me but get a systemd tutorial or howto. I am sure Ubuntu or Debian have one, or the Arch Linux wiki, or the official Red Hat documentation.
Thanks very much but this still did not work. I copied file from /lib to /etc and added the necessary in the Unit section. I rebooted the Pi and the OpenVPN is running but I cannot connect. I reload the service and it connects almost simultaneously.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.