[systemd-devel] Failed at step RUNTIME_DIRECTORY spawning /usr/bin/true: File exists

[Lennart Poettering]

On Thu, 06.08.15 10:57, Reindl Harald (h.reindl at thelounge.net) wrote:

> >So, you'll get this EEXIST error only if there's already something at
> >the place of the runtime dir that is either:
> 
> NOBODY but systemd creates that directory
> it don't exist at all before the service is started
> 
> the problem is that SOMETIMES at stop is
> seems not to be removed and so the next start
> fails

Whether it is removed or not should not matter really, the code is
completely fine already exists as long as the uid/gid/mode match (as
mentioned before).

> the second problem is that SOMETIMES systemd creates
> RuntimeDirectory for ExecStart *and* ExecStartPost
> and if that happens ExecStartPost fails and so the
> service too which is killed hence while the main
> process is already running fine
> 
> you *really* should look at
> https://bugzilla.redhat.com/show_bug.cgi?id=1226509#c3

Any chance you can reduce this to a minimal test case? The unit file
has a lot of settings that are almost certainly unrelated to the issue
at hand?

> >It would be good if you could verify that file data of the runtime dir
> >when this fails for you. Thanks.

I'd still like to see the permission and ownership of the runtime dir
when this failed.

Lennart

-- 
Lennart Poettering, Red Hat