I'm running systemd 215 on a fairly up-to-date Debian Jessie system. I have a Type=forking service that fails on its first ExecStartPre command which is using /bin/mkdir to create a directory.
The service fails to start with the following. Apr 13 10:07:42 localhost systemd[1]: Starting OVSDB Server Daemon... Apr 13 10:07:42 localhost systemd[4069]: Failed at step CHDIR spawning /bin/mkdir: No such file or directory Apr 13 10:07:42 localhost systemd[1]: ovsdb-server.service: control process exited, code=exited status=200 Job for ovsdb-server.service failed. See 'systemctl status ovsdb-server.service' and 'journalctl -xn' for details. Apr 13 10:07:42 localhost systemd[1]: Failed to start OVSDB Server Daemon. Apr 13 10:07:42 localhost systemd[1]: Unit ovsdb-server.service entered failed state. a I've verified that '/bin/mkdir' does exist and does run fine. So I assume the the 'No such file or directory' refers to the target of the chdir. My question is how do I troubleshoot from here? What can I do to determine exactly what file or directory is not being found. I'd like to understand what is wrong and fix it. Thanks and Regards, Mike
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel