Re: systemctl openvpn won't start

2017-11-26 Thread Ulf Volmer
On 26.11.2017 20:32, Bill Shirley wrote: > Yes, a symlink you mentioned will probably work for him. > > From the link you posted: > > |sudo systemctl edit --full nginx.service | in general i think removing --full from this line will be much better. This command will create /etc/systemd/system/

Re: systemctl openvpn won't start

2017-11-26 Thread Bill Shirley
Yes, a symlink you mentioned will probably work for him. From the link you posted: |sudo systemctl edit --full nginx.service | This will load the current unit file into the editor, where it can be modified. When the editor exits, the changed file will be written to |/etc/systemd/system|, which

Re: systemctl openvpn won't start

2017-11-26 Thread Ulf Volmer
On 26.11.2017 19:26, Bill Shirley wrote: > Corrupt?  Take a look at > https://www.freedesktop.org/software/systemd/man/systemd.unit.html : Please do not top post. First of all, we are talking about instanced units. There is no need to copy anything to /etc/systemd. Just a symlink to the original

Re: systemctl openvpn won't start

2017-11-26 Thread Bill Shirley
Corrupt?  Take a look at https://www.freedesktop.org/software/systemd/man/systemd.unit.html : The first possibility is to copy the unit file to|/etc/systemd/system/httpd.service|and change the chosen settings: [Unit] Description=Some HTTP server After=remote-fs.target sqldb.service /memcached.

Re: systemctl openvpn won't start

2017-11-26 Thread Ulf Volmer
On 26.11.2017 18:45, Bill Shirley wrote: > I don't know why, but it doesn't seem to be working for him.  From an > earlier post: >> sudo systemctl enable openvpn-client@ibecker2.service >> Failed to enable unit: Unit file openvpn-client@ibecker2.service does not >> exist. Yes, i have read the earl

Re: systemctl openvpn won't start

2017-11-26 Thread Bill Shirley
I don't know why, but it doesn't seem to be working for him.  From an earlier post: sudo systemctl enableopenvpn-client@ibecker2.service Failed to enable unit: Unit fileopenvpn-client@ibecker2.service does not exist. Bill On 11/26/2017 10:44 AM, Ulf Volmer wrote: On 26.11.2017 16:07, Bill S

Re: systemctl openvpn won't start

2017-11-26 Thread Ulf Volmer
On 26.11.2017 16:07, Bill Shirley wrote: > For you, you should: > cp -a /usr/lib/systemd/system/openvpn-client@.service > /etc/systemd/system/openvpn-client@ibecker2.service > systemctl daemon-reload That is normally not needed, systemctl should create the symlinks himself. [ulf@x1 ~]$ sudo syst

Re: systemctl openvpn won't start

2017-11-26 Thread Bill Shirley
An explanation of systemd template files: https://fedoramagazine.org/systemd-template-unit-files/ For you, you should: cp -a /usr/lib/systemd/system/openvpn-client@.service /etc/systemd/system/openvpn-client@ibecker2.service systemctl daemon-reload systemctl start openvpn-client@ibecker2.service

Re: systemctl openvpn won't start

2017-11-25 Thread Neal Becker
Ulf Volmer wrote: > On 23.11.2017 13:34, Neal Becker wrote: > >> sudo systemctl enable openvpn-client@ibecker2.service >> Failed to enable unit: Unit file openvpn-client@ibecker2.service does not >> exist. > > interesting. Could you post the output of > > rpm -ql openvpn|grep service > > best

Re: systemctl openvpn won't start

2017-11-23 Thread Ulf Volmer
On 23.11.2017 13:34, Neal Becker wrote: > sudo systemctl enable openvpn-client@ibecker2.service > Failed to enable unit: Unit file openvpn-client@ibecker2.service does not > exist. interesting. Could you post the output of rpm -ql openvpn|grep service best regards Ulf _

Re: systemctl openvpn won't start

2017-11-23 Thread Neal Becker
Ulf Volmer wrote: > On 23.11.2017 12:54, Neal Becker wrote: > >> Oh, thanks! And what should be in openvpn-client@ibecker2.service? Is >> it just a symlink to the template file openvpn-client@.service? > > Yes. You should normally create this symlinks by using > systemctl enable openvpn-client

Re: systemctl openvpn won't start

2017-11-23 Thread Ulf Volmer
On 23.11.2017 12:54, Neal Becker wrote: > Oh, thanks! And what should be in openvpn-client@ibecker2.service? Is it > just a symlink to the template file openvpn-client@.service? Yes. You should normally create this symlinks by using systemctl enable openvpn-client@ibecker2.service best regard

Re: systemctl openvpn won't start

2017-11-23 Thread Neal Becker
Ulf Volmer wrote: > On 22.11.2017 20:59, Bill Shirley wrote: > >> What we've been talking about is the unit file >> (openvpn@client-ibecker2.service). > > Since fc26 (if i remembered correctly) there were separate systemd units > for openvpn server and client configurations. > > /usr/lib/system

Re: systemctl openvpn won't start

2017-11-22 Thread Kseniya Blashchuk
I have just moved all configs and certificates to /etc/openvpn/client/. And I launch the client as 'systemctl start openvpn-client@myconnection' On Thu, Nov 23, 2017, 12:02 AM Ulf Volmer wrote: > On 22.11.2017 20:59, Bill Shirley wrote: > > > What we've been talking about is the unit file > > (o

Re: systemctl openvpn won't start

2017-11-22 Thread Ulf Volmer
On 22.11.2017 20:59, Bill Shirley wrote: > What we've been talking about is the unit file > (openvpn@client-ibecker2.service). Since fc26 (if i remembered correctly) there were separate systemd units for openvpn server and client configurations. /usr/lib/systemd/system/openvpn-client@.service /u

Re: systemctl openvpn won't start

2017-11-22 Thread Bill Shirley
That link is for something different.  It's automatically created by the systemctl enable command.  I have one too: [0:root@elmo ~]$ ls -lZ /etc/systemd/system/multi-user.target.wants/openvpn@server.service lrwxrwxrwx. 1 root root system_u:object_r:systemd_unit_file_t:s0 42 Jul 17  2015 /etc/sys

Re: systemctl openvpn won't start

2017-11-22 Thread Neal Becker
Bill Shirley wrote: > Is the .service file in /etc/systemd/system ? > [0:root@elmo ~ 2]$ ls -lZ /etc/systemd/system/openvpn@server.service > -rw-r--r--. 1 root root system_u:object_r:systemd_unit_file_t:s0 148 Aug > 6 2015 /etc/systemd/system/openvpn@server.service Of course yours would > be ope

Re: systemctl openvpn won't start

2017-11-22 Thread Bill Shirley
Putting your localized file in /lib/systemd/system is the problem. The upgrade wiped it out.  Localizations should go in /etc/systemd/system The Fedora 25 /lib/systemd/system/openvpn.service unit file from the rpm: [Unit] Description=OpenVPN Robust And Highly Flexible Tunneling Application On %I

Re: systemctl openvpn won't start

2017-11-22 Thread Outback Dingo
yeah somethings changed it used to be simple now we have to create/copy files to systemd i just went through this today also specifically in Section 5. Setting up automatic OpenVPN connection on system start *This step requires that you set up automatic login from the previous step. https://h

Re: systemctl openvpn won't start

2017-11-22 Thread Bill Shirley
Is the .service file in /etc/systemd/system ? [0:root@elmo ~ 2]$ ls -lZ /etc/systemd/system/openvpn@server.service -rw-r--r--. 1 root root system_u:object_r:systemd_unit_file_t:s0 148 Aug  6  2015 /etc/systemd/system/openvpn@server.service Of course yours would be openvpn@client-ibecker2.service

systemctl openvpn won't start

2017-11-22 Thread Neal Becker
Was working before upgrade to f27. Now: sudo systemctl start openvpn@client-ibecker2 Failed to start openvpn@client-ibecker2.service: Unit openvpn@client- ibecker2.service not found. According to https://fedoraproject.org/wiki/Openvpn#Working_with_systemd I would need to have /etc/openvpn/clien