6
[Solved] How can I make a custom .service run as root?
(reddthat.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Jul 2024
6 points (87.5% liked)
Linux Questions
1061 readers
2 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 1 year ago
MODERATORS
Private Internet Access
I assume so, but just to be sure, have you run
sudo systemctl enable blah.servicethen reboot? It'll symbolic link to the systemd auto start service and run it at boot.Also, make sure everything is marked as executable; especially whatever you have "/path/to/daemon" set as.
sudo chmod +x /path/to/daemonRestart the service or reboot then :
sudo systemctl status blah.serviceYep, more specifically I tried
sudo systemctl enable --now daemon.service. Gives the same error, and maybe that's because it's some kind of binary.sudo /bin/bash /path/to/daemonthrows the same error, butsudo /path/to/daemondoes not. However, if I drop ,/bin/bashfrom the service file, it throws a 203 error instead.Is the daemon a binary? If so drop the bash part and try
sudo chmod 755 /path/to/daemon.Tried that, back to 203/Exec error. It's like ExecStart wants me to specify a program to launch it, and bash clearly isn't it.
Try
ExecStart=/usr/bin/env /path/to/daemonAlso what's the output of
ldd /path/to/daemon&sudo systemd-run /path/to/daemon? Maybe checksystemctl show-environment. Maybe try addingType=simple, this tells systemd that the service will fork.If that fails, we could try
ExecStart=/usr/bin/strace -f -o /tmp/daemon_strace.log /path/to/daemonfor stactrace &ExecStart=/bin/sh -c '/path/to/daemon > /tmp/daemon.log 2>&1'to log the daemon.Omg, adding
/usr/bin/envworked. Launched the daemon, and the client is able to launch and connect a WireGuard tunnel.systemctl show-environmentlists/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbinon the PATH, so maybe that's why that worked...? (I'm going to have to go read up onenv).Either way, I did a reboot to verify, and it's definitely running. Now I just need to tweak it a bit so it tries to reconnect if the network drops out, but holy shit, I appreciate the help.
Good to hear that it worked.
To explain env, typically when systemd is running a service it only provides a very minimal environment. When using env it passes more of the environment variables and whatnot from userspace, so it's likely that the binary daemon was looking for specific environment variables and it returned an empty string and that's what caused error, it's also useful if the daemon's location changes during runtime or if it's not in a standard location.