what causes “systemd: Failed at step USER spawning /usr/sbin/opendkim: No such process”

up vote
10
down vote

favorite

Anybody here tell me how to 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.

asked Dec 15 '16 at 5:38

Syed

51114

add a comment |

up vote
10
down vote

favorite

Anybody here tell me how to 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.

asked Dec 15 '16 at 5:38

Syed

51114

add a comment |

up vote
10
down vote

favorite

Anybody here tell me how to 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.

asked Dec 15 '16 at 5:38

Syed

51114

Anybody here tell me how to 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.

linux

asked Dec 15 '16 at 5:38

Syed

51114

asked Dec 15 '16 at 5:38

Syed

51114

asked Dec 15 '16 at 5:38

Syed

51114

asked Dec 15 '16 at 5:38

Syed

51114

asked Dec 15 '16 at 5:38

Syed

51114

add a comment |

4 Answers
4

active

oldest

votes

up vote
7
down vote

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:

[Service]

User=tadeusz

answered Jul 18 '17 at 14:12

Tadeusz Łazurski

20127

Thanks. In my case the name was completely wrong, and this solves this problem for me very nicely
– Aleks
Apr 13 at 1:06

After pulling my hair for long 4 hours I came across this post and just removed User=tomcat which I copied from blog post. Now it works fine :)
– Shashanth
Aug 27 at 10:18

I got similar problem, fixing the username doesn't work, because gunicorn file is not present in virtualenv. I installed using- sudo pip3 install gunicorn in AWS EC2 ubuntu server. what could be possible reason?
– Reema Parakh
Nov 22 at 6:36

add a comment |

up vote
4
down vote

Check if the following record exists in the configuration file of opendkim:

## Attempt to become the specified user before starting operations. UserID opendkim:opendkim

edited Dec 28 '16 at 14:53

Kamil Maciorowski

22.7k155072

answered Dec 28 '16 at 6:04

user679441

411

add a comment |

up vote
0
down vote

For me this error message was caused by not reloading SystemD after updating systemd. So run # systemctl daemon-reload or reboot your computer.

edited Aug 18 at 16:16

answered Aug 15 at 15:02

Babken Vardanyan

6501513

1

sudo systemctl daemon-reload should be enough
– dvska
Aug 17 at 15:40

@dvska Thanks, added that to the answer.
– Babken Vardanyan
Aug 18 at 16:16

add a comment |

up vote
0
down vote

For me it was a simple issue of using the wrong user name, confirm you are using right user
[Service] User=tadeusz

then reload your SytemD sudo systemctl daemon-reload

answered Nov 21 at 4:09

StackEdd

New contributor

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1156676%2fwhat-causes-systemd-failed-at-step-user-spawning-usr-sbin-opendkim-no-such-p%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

4 Answers
4

active

oldest

votes

4 Answers
4

active

oldest

votes

up vote
7
down vote

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:

[Service]

User=tadeusz

answered Jul 18 '17 at 14:12

Tadeusz Łazurski

20127

Thanks. In my case the name was completely wrong, and this solves this problem for me very nicely
– Aleks
Apr 13 at 1:06

After pulling my hair for long 4 hours I came across this post and just removed User=tomcat which I copied from blog post. Now it works fine :)
– Shashanth
Aug 27 at 10:18

I got similar problem, fixing the username doesn't work, because gunicorn file is not present in virtualenv. I installed using- sudo pip3 install gunicorn in AWS EC2 ubuntu server. what could be possible reason?
– Reema Parakh
Nov 22 at 6:36

add a comment |

up vote
7
down vote

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:

[Service]

User=tadeusz

answered Jul 18 '17 at 14:12

Tadeusz Łazurski

20127

Thanks. In my case the name was completely wrong, and this solves this problem for me very nicely
– Aleks
Apr 13 at 1:06

After pulling my hair for long 4 hours I came across this post and just removed User=tomcat which I copied from blog post. Now it works fine :)
– Shashanth
Aug 27 at 10:18

I got similar problem, fixing the username doesn't work, because gunicorn file is not present in virtualenv. I installed using- sudo pip3 install gunicorn in AWS EC2 ubuntu server. what could be possible reason?
– Reema Parakh
Nov 22 at 6:36

add a comment |

up vote
7
down vote

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:

[Service]

User=tadeusz

answered Jul 18 '17 at 14:12

Tadeusz Łazurski

20127

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:

[Service]

User=tadeusz

answered Jul 18 '17 at 14:12

Tadeusz Łazurski

20127

answered Jul 18 '17 at 14:12

Tadeusz Łazurski

20127

answered Jul 18 '17 at 14:12

Tadeusz Łazurski

20127

answered Jul 18 '17 at 14:12

Tadeusz Łazurski

20127

Thanks. In my case the name was completely wrong, and this solves this problem for me very nicely
– Aleks
Apr 13 at 1:06

After pulling my hair for long 4 hours I came across this post and just removed User=tomcat which I copied from blog post. Now it works fine :)
– Shashanth
Aug 27 at 10:18

I got similar problem, fixing the username doesn't work, because gunicorn file is not present in virtualenv. I installed using- sudo pip3 install gunicorn in AWS EC2 ubuntu server. what could be possible reason?
– Reema Parakh
Nov 22 at 6:36

add a comment |

Thanks. In my case the name was completely wrong, and this solves this problem for me very nicely
– Aleks
Apr 13 at 1:06

After pulling my hair for long 4 hours I came across this post and just removed User=tomcat which I copied from blog post. Now it works fine :)
– Shashanth
Aug 27 at 10:18

I got similar problem, fixing the username doesn't work, because gunicorn file is not present in virtualenv. I installed using- sudo pip3 install gunicorn in AWS EC2 ubuntu server. what could be possible reason?
– Reema Parakh
Nov 22 at 6:36

Thanks. In my case the name was completely wrong, and this solves this problem for me very nicely
– Aleks
Apr 13 at 1:06

After pulling my hair for long 4 hours I came across this post and just removed User=tomcat which I copied from blog post. Now it works fine :)
– Shashanth
Aug 27 at 10:18

I got similar problem, fixing the username doesn't work, because gunicorn file is not present in virtualenv. I installed using- sudo pip3 install gunicorn in AWS EC2 ubuntu server. what could be possible reason?
– Reema Parakh
Nov 22 at 6:36

add a comment |

up vote
4
down vote

Check if the following record exists in the configuration file of opendkim:

## Attempt to become the specified user before starting operations. UserID opendkim:opendkim

edited Dec 28 '16 at 14:53

Kamil Maciorowski

22.7k155072

answered Dec 28 '16 at 6:04

user679441

411

add a comment |

up vote
4
down vote

Check if the following record exists in the configuration file of opendkim:

## Attempt to become the specified user before starting operations. UserID opendkim:opendkim

edited Dec 28 '16 at 14:53

Kamil Maciorowski

22.7k155072

answered Dec 28 '16 at 6:04

user679441

411

add a comment |

up vote
4
down vote

Check if the following record exists in the configuration file of opendkim:

## Attempt to become the specified user before starting operations. UserID opendkim:opendkim

edited Dec 28 '16 at 14:53

Kamil Maciorowski

22.7k155072

answered Dec 28 '16 at 6:04

user679441

411

Check if the following record exists in the configuration file of opendkim:

## Attempt to become the specified user before starting operations. UserID opendkim:opendkim

edited Dec 28 '16 at 14:53

Kamil Maciorowski

22.7k155072

answered Dec 28 '16 at 6:04

user679441

411

edited Dec 28 '16 at 14:53

Kamil Maciorowski

22.7k155072

edited Dec 28 '16 at 14:53

Kamil Maciorowski

22.7k155072

edited Dec 28 '16 at 14:53

Kamil Maciorowski

22.7k155072

answered Dec 28 '16 at 6:04

user679441

411

answered Dec 28 '16 at 6:04

user679441

411

answered Dec 28 '16 at 6:04

user679441

411

add a comment |

up vote
0
down vote

For me this error message was caused by not reloading SystemD after updating systemd. So run # systemctl daemon-reload or reboot your computer.

edited Aug 18 at 16:16

answered Aug 15 at 15:02

Babken Vardanyan

6501513

1

sudo systemctl daemon-reload should be enough
– dvska
Aug 17 at 15:40

@dvska Thanks, added that to the answer.
– Babken Vardanyan
Aug 18 at 16:16

add a comment |

up vote
0
down vote

For me this error message was caused by not reloading SystemD after updating systemd. So run # systemctl daemon-reload or reboot your computer.

edited Aug 18 at 16:16

answered Aug 15 at 15:02

Babken Vardanyan

6501513

1

sudo systemctl daemon-reload should be enough
– dvska
Aug 17 at 15:40

@dvska Thanks, added that to the answer.
– Babken Vardanyan
Aug 18 at 16:16

add a comment |

up vote
0
down vote

For me this error message was caused by not reloading SystemD after updating systemd. So run # systemctl daemon-reload or reboot your computer.

edited Aug 18 at 16:16

answered Aug 15 at 15:02

Babken Vardanyan

6501513

For me this error message was caused by not reloading SystemD after updating systemd. So run # systemctl daemon-reload or reboot your computer.

edited Aug 18 at 16:16

answered Aug 15 at 15:02

Babken Vardanyan

6501513

edited Aug 18 at 16:16

answered Aug 15 at 15:02

Babken Vardanyan

6501513

answered Aug 15 at 15:02

Babken Vardanyan

6501513

answered Aug 15 at 15:02

Babken Vardanyan

6501513

1

sudo systemctl daemon-reload should be enough
– dvska
Aug 17 at 15:40

@dvska Thanks, added that to the answer.
– Babken Vardanyan
Aug 18 at 16:16

add a comment |

1

sudo systemctl daemon-reload should be enough
– dvska
Aug 17 at 15:40

@dvska Thanks, added that to the answer.
– Babken Vardanyan
Aug 18 at 16:16

sudo systemctl daemon-reload should be enough
– dvska
Aug 17 at 15:40

@dvska Thanks, added that to the answer.
– Babken Vardanyan
Aug 18 at 16:16

add a comment |

up vote
0
down vote

For me it was a simple issue of using the wrong user name, confirm you are using right user
[Service] User=tadeusz

then reload your SytemD sudo systemctl daemon-reload

answered Nov 21 at 4:09

StackEdd

New contributor

add a comment |

up vote
0
down vote

For me it was a simple issue of using the wrong user name, confirm you are using right user
[Service] User=tadeusz

then reload your SytemD sudo systemctl daemon-reload

answered Nov 21 at 4:09

StackEdd

New contributor

add a comment |

up vote
0
down vote

For me it was a simple issue of using the wrong user name, confirm you are using right user
[Service] User=tadeusz

then reload your SytemD sudo systemctl daemon-reload

answered Nov 21 at 4:09

StackEdd

New contributor

For me it was a simple issue of using the wrong user name, confirm you are using right user
[Service] User=tadeusz

then reload your SytemD sudo systemctl daemon-reload

answered Nov 21 at 4:09

StackEdd

New contributor

answered Nov 21 at 4:09

StackEdd

New contributor

answered Nov 21 at 4:09

StackEdd

answered Nov 21 at 4:09

StackEdd

New contributor

StackEdd is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment |

draft saved

draft discarded

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Argthtjtr