How can I remove following error:
systemd: Failed at step USER spawning /usr/sbin/opendkim: No such process
It occurs when I try to start opendkim service on Centos.
Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up.Sign up to join this community
I've just ran into this and in my case it was caused by quoting a user name in my service file:
[Unit] Description=Demonstrate Failed at step USER spawning ...: No such process error when user name is quoted [Service] User="tadeusz" ExecStart=/bin/echo hello [Install] WantedBy=multi-user.target
Starting this service on Ubuntu 16.04.2 LTS (Amazon EC2 instance) would fail with following error:
user-example.service: Failed at step USER spawning /bin/echo: No such process
Interestingly, on Ubuntu Gnome 17.04 (my local machine), the error message is much more helpful:
[/etc/systemd/system/user-example.service:5] Invalid user/group name or numeric ID, ignoring: "tadeusz"
Removing quotes in both environments resolved the problem:
For me with that error message, turns out I was specifying "User=root" but not "Group=xx", so when I specified both it fixed it:
so either adding
Group=root or getting rid of both User= and Group=, as suggested in jmunsch's answer, fixed it. There was some kind of directory permission issue without specifying Group.
I guess if you specify a User then it doesn't use the default Group, which I presume is also root? Though the default is supposed to be
User=root and the default group is supposed to be that user's default group, so not sure if this is expected.
It is also helpful, regardless the message, to check
journalctl for any logs or any indications of what might have gone wrong. If it's "217/USER" then it won't show much in there for diagnosing but for everything else it can have super helpful info.
For me it was solved by commenting "User" and "Group" directives in the service file as described here. I hope it helps somebody.
In my case I've been getting the error when using
It turns out that my version of
systemd is too old. From https://0pointer.net/blog/dynamic-users-with-systemd.html:
... we released systemd 235. Among other improvements this greatly extends the dynamic user logic of systemd. Dynamic users are a powerful but little known concept, supported in its basic form since systemd 232. With this blog story I hope to make it a bit better known.
Ran into this message, but only at boot time, starting it manually it started fine.
My hunch is that it was caused by "active directory" (where this particular box gets some of its usernames and groups) not having been fully initiated yet, so adding a
Seems to have fixed it by making it start late enough.
After=mnt-share.mount also seemed to work around the problem, but I think possibly because it just happened to "also wait long enough" or something. Or
systemctl status xxx said:
Failed at spawning... [?] Process: 5017 ExecStart=/home/user/bin/xx (code=exited, status=217/USER)
Same situation with @rogerdpack, all we need is waiting enough time for AD ready. But there is no luck for me on
After=vasd.service After=mnt-share.mount After=nss-user-lookup.target
So I checked the bootup time usage with
Choose the latest one or add below works for me.