Linux Questions

4118 readers

5 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

stay on topic
be nice (no name calling)
do not post long blocks of text such as logs
do not delete your posts
only post questions (no information posts)

Tips for giving and receiving help

be as clear and specific
say thank you if a solution works
verify your solutions before posting them as facts.

Any rule violations will result in disciplinary actions

founded 3 years ago

MODERATORS

possiblylinux127@lemmy.zip

[Solved] How can I make a custom .service run as root? (reddthat.com)

submitted 2 years ago* (last edited 2 years ago) by Telorand@reddthat.com to c/linuxquestions@lemmy.zip

13 comments fedilink hide all child comments

cross-posted from: https://reddthat.com/post/21668140

I have a VPN daemon that needs to run before the client will work. Normally, this would have been set up automatically by its install script, but the system is immutable.

I've created the systemd service via sysyemctl edit --force --full daemon.service with the following parameters:
[Unit] 
Description=Blah
After=network-online.target

[Service]
User=root
Group=root
ExecStart=/usr/bin/env /path/to/daemon

[Install]
WantedBy=multi-user.target
I've verified that the daemon is actually executable, and it runs fine when I manually call it via sudo daemon. When I try to run it with sudo systemctl enable --now daemon.service, it exits with error code 126.

What am I missing?

Edit: Typo, and added the relevant user and group to the Service section. Still throwing a 126.

Solution: the system wanted /usr/bin/env in ExecStart to launch the binary. The .service file above has been edited to show the working solution.

all 19 comments

sorted by: hot top controversial new old

[–] nhowell77@sh.itjust.works 3 points 2 years ago* (last edited 2 years ago) (4 children)

If that is your full .service file you are missing the directive to tell the daemon what user to run under. Under service try adding

User=root

Group=root

Before the ExecStart command line.

[–] Successful_Try543@feddit.org 4 points 2 years ago* (last edited 2 years ago) (2 children)

Is that necessary for processes running as root? AfaIk, root is default.

Keywords should be in CamelCase format, thus the space in Wanted By is wrong.

[–] nhowell77@sh.itjust.works 3 points 2 years ago (1 children)

Honestly can't believe I completely missed the space in Wanted By. This is likely the bigger culprit to the failed to run error. Poster above me is correct should read

WantedBy

[–] Telorand@reddthat.com 2 points 2 years ago (1 children)

It's an autocorrect typo. It's actually WantedBy in the file.

[–] Successful_Try543@feddit.org 2 points 2 years ago

Would have been nice if this would have been the error.

[–] Telorand@reddthat.com 2 points 2 years ago

Foiled by autocorrect! There's no space in the original file, and I've edited my post to reflect that.

[–] Successful_Try543@feddit.org 1 points 2 years ago* (last edited 2 years ago)

Does the command in ExecStart work in a root environment, e.g. sudo -i?

[–] Telorand@reddthat.com 1 points 2 years ago

I added the relevant user and group, and it's still throwing a 126. I checked the daemon itself, and it looks like it's a pre-compiled binary. Manually running /bin/bash /path/to/daemon gives the same error, but sudo /path/to/daemon starts the daemon.