systemd start job fails without leaving reason
by Turbocapitalist from LinuxQuestions.org on (#4SQJY)
I have another systemd problem. A start job is failing and journalctl -xe is providing unuseful notices like these:
Code:. . .
-- The process' exit code is 'exited' and its exit status is 1.
. . .
-- The unit foo.service has entered the 'failed' state with result 'exit-code'.
. . .
-- The job identifier is 168 and the job result is failed.
. . .This start job needs to happen fairly early in the boot process. If I were to guess, I might say I have to move it back after some other service.
How do I get systemd provide any useful information that would help finding the reason why the job has failed?
Code:# systemctl show 168
Failed to get properties: Unknown object '/org/freedesktop/systemd1/job/168'.
Code:. . .
-- The process' exit code is 'exited' and its exit status is 1.
. . .
-- The unit foo.service has entered the 'failed' state with result 'exit-code'.
. . .
-- The job identifier is 168 and the job result is failed.
. . .This start job needs to happen fairly early in the boot process. If I were to guess, I might say I have to move it back after some other service.
How do I get systemd provide any useful information that would help finding the reason why the job has failed?
Code:# systemctl show 168
Failed to get properties: Unknown object '/org/freedesktop/systemd1/job/168'.