Hide Forgot
Description of problem: # systemctl status openvpn.service openvpn.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) # service openvpn restart Redirecting to /bin/systemctl restart openvpn.service Failed to issue method call: Unit openvpn.service failed to load: No such file or directory. See system logs and 'systemctl status openvpn.service' for details. # rpm -ql openvpn | grep -i service /lib/systemd/system/openvpn@.service # systemctl status openvpn@.service Failed to issue method call: Unit name openvpn@.service is not valid. Version-Release number of selected component (if applicable): # rpm -q openvpn openvpn-2.2.1-2.fc16.x86_64 How reproducible: Always
It works by: # systemctl start openvpn But it is difficult to guess it.
Hm... Very interesting. In what man it mentioned??? How users should guess it? How restart all hosts?
I found it in the Bug 744244.
It does start that way, but how do I enable it as a service? [root@veselo openvpn]# systemctl start openvpn [root@veselo openvpn]# echo $? 0 [root@veselo openvpn]# systemctl enable openvpn Failed to issue method call: No such file or directory
For this there is no support in systemctl. Manually creating the symlinks in the right directories will work though. *** This bug has been marked as a duplicate of bug 752774 ***