Hello, Description of problem: As of September 10th, 2015, tinc's initialization via systemd mechanism seems to be broken. A tincd.target file is *not* installed by the stock .rpm package. An /etc/sysconfig/tinc configuration file is *not* created by the stock .rpm package (this would allow user to set tinc's various initialization parameters, such as the mandatory network/VPN name). If the tincd service is started manually (or via a script run from the obsoleted /etc/rc.d/rc.local), the command "systemctl list-unit-files --type=service" says tincd@.service disabled but the tincd service *cannot* be managed via regular systemctl commands (enable/disable/start/stop/reload etc.). Version-Release number of selected component (if applicable): tinc-1.0.24-6.el7.x86_64 (stock package from EPEL7 running on CentOS 7.x) How reproducible: Always. Steps to Reproduce: 1. On a systemd-enabled system, install tinc package from EPEL 2. Try to start tincd service via "system start tincd" Actual results: 1. Cannot manage tincd via systemctl commands (enable/disable/start/stop/reload etc.). 2. The rpm package installs no /etc/sysconfig/tincd file, as a standard configuration place (file) where to set initialization parameters such as the VPN's name Expected results: 1. tincd service should be smoothly manageable via regular systemctl commands (enable/disable/start/stop/reload etc.). Stock RPM package should install all systemd initialization files in proper places. 2. A preconfigured /etc/sysconfig/tincd file should be installed by the RPM package, as a standard place where to set initialization parameters such as the VPN's name. (Most common) parameters in the /etc/sysconfig/tincd file should be present, commented out (and documented in the man page). Additional info: Please see older EPEL's bug #1161033 https://bugzilla.redhat.com/show_bug.cgi?id=1161033 Best regards, Răzvan
Please see also bug #1078237 Răzvan
Hi Răzvan, The service has an '@' after its name, means it is an unit template and it asked for a parameter, which in this case, is the name of the VPN profile. See also: https://fedoramagazine.org/systemd-template-unit-files/ http://superuser.com/questions/393423/the-symbol-and-systemctl-and-vsftpd Regards, Chen
All related: https://bugzilla.redhat.com/show_bug.cgi?id=1373704 https://bugzilla.redhat.com/show_bug.cgi?id=1394512 https://github.com/gsliepen/tinc/issues/133
Hello, This seem to be fixed in CentOS 7.3 (1611), as of February 16th, 2017. Tinc service starts correctly at boot, provided that one enables both "tinc" and "tinc@network" in systemd. Best regards, Răzvan
So we need tinc and tinc@netname both enabled? Good to know that. I'll give it a try.
Checked and worked. Since both reporters (Răzvan and me) observed fixed, I suggest close this bug as closed errata.