FS#32419 - [dante] starting/working as a service in systemd
Attached to Project:
Community Packages
Opened by Shahab (shahab) - Saturday, 03 November 2012, 10:49 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 06 November 2012, 11:16 GMT
Opened by Shahab (shahab) - Saturday, 03 November 2012, 10:49 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 06 November 2012, 11:16 GMT
|
Details
Description:
It is not possible to start/enable the sockd in systemd systems. the problem is because of the mentioned field in "/usr/lib/systemd/system/sockd.service": ... [Service] ... ExecStart=sockd $SOCKD_OPTS ... it must use the full path: ExecStart=/usr/sbin/sockd $SOCKD_OPTS Additional info: * package version(s): 1.3.2-2 Steps to reproduce: > systemctl start sockd.service Failed to issue method call: Unit sockd.service failed to load: Invalid argument. See system logs and 'systemctl status sockd.service' for details. > journalctl ... systemd[1]: [/usr/lib/systemd/system/sockd.service:8] Invalid executable path in command line, ignoring: sockd $SOCKD_OPTS systemd[1]: sockd.service lacks ExecStart setting. Refusing. ... |
This task depends upon
During the system boot, it must be loaded after eth0 (or any related) interface
is up:
-----------------------------------------------------------------------------
sockd[131]: warning: ifname2sockaddr(): ifname eth0 has no ipv4 addresses configured. Not usable
sockd[131]: warning: could not resolve name eth0: Unknown host
sockd[131]: warning: ifname2sockaddr(): ifname eth0 has no ipv4 addresses configured. Not usable
sockd[131]: error: /etc/sockd.conf: error on line xx, near "eth0": could not resolve eth0: Unknown host
sockd[131]: alert: sockdexit(): terminating
sockd[131]: warning: sockdexit(): truncate(/var/run/sockd.pid): No such file or directory (errno = 2)
-----------------------------------------------------------------------------