systemctl start blocky fails with 217 USER

Question

systemctl start blocky fails with 217 USER

yusi1 opened this issue 2 years ago · comments

● blocky.service - Blocky is a DNS proxy and ad-blocker
     Loaded: loaded (/etc/systemd/system/blocky.service; enabled; vendor preset>
     Active: activating (auto-restart) (Result: exit-code) since Fri 2022-06-03>
    Process: 28997 ExecStart=/opt/blocky/blocky --config /opt/blocky/config.yml>
   Main PID: 28997 (code=exited, status=217/USER)
        CPU: 839us

Yusef Aslam · Answer 1 · Sat Jun 04 2022 00:42:31 GMT+0800 (China Standard Time)

Fixed with useradd blockyusr.

/:) · Answer 2 · Sat Jun 04 2022 00:47:29 GMT+0800 (China Standard Time)

Hi, thanks for your reply? it is a strange as is installer use useradd tool in the installation process and blockyusr should be created automatically.

P.S. You also can use journalctl or debug mode in blocky or system messages for possible diagnostic or troubleshoot some problems.

Yusef Aslam · Answer 3 · Sat Jun 04 2022 01:04:55 GMT+0800 (China Standard Time)

I don't know what happened to be honest, also the capabilities on the blocky executable file were reset too so I had to add them again with:
setcap CAP_NET_BIND_SERVICE+ep blocky

Yusef Aslam · Answer 4 · Sat Jun 04 2022 01:06:04 GMT+0800 (China Standard Time)

thanks for the tip for debug mode too btw I will use that next time

Yusef Aslam · Answer 5 · Sat Jun 04 2022 01:10:43 GMT+0800 (China Standard Time)

Also I had blocky already installed in /opt with my config before I ran the script, maybe that might of caused some issue?

/:) · Answer 6 · Sat Jun 04 2022 20:19:23 GMT+0800 (China Standard Time)

Potentially yes, since a systemd unit is created that runs as the blockyusr user and you need to restart installed blocky with special installed script restart-blocky.sh this script set permit to setcap to blockyusr

Yusef Aslam · Answer 7 · Tue Jun 07 2022 16:27:01 GMT+0800 (China Standard Time)

I'll use that script to restart Blocky next time, thanks.