0xERR0R/blocky

Unable to create Systemd Service

ChitranshuV opened this issue · 5 comments

ChitranshuV commented

I setup Blocky successfully on my Linux machine after following these steps - #1615 (comment)

Now the problem I am facing is starting Blocky as a systemd service. I am unable to find the cause of the error. Starting Blocky from the CLI usually works fine, but it doesn't start when using the systemd service. I'm not sure, but maybe the reason is that the internet is not available before I connect to the Blocky server, which means it can't download the blocklists. I have seen this error a few times though:

WARN list_cache: Can't download file: Get "https://big.oisd.nl/domainswild": dial tcp [2001:41d0:701:1100::5b10]:443: connect: network is unreachable attempt=1/5 link=https://big.oisd.nl/domainswild

and then this will fail eventually after all the retry attempts, but changing the cooldown and timeout parameters in config.yml fixed it for me and I mostly don't see any of these warnings or errors.

[PATH] here is folder where Blocky is installed, and [USERNAME] is Linux username

$ cat /etc/systemd/system/blocky.service
[Unit]
Description=Blocky DNS proxy
After=network-online.target

[Service]
User=[USERNAME]
ExecStart=/[PATH]/blocky --config /[PATH]/config.yml
Restart=on-failure

[Install]
WantedBy=network-online.target

$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 127.0.0.1

$ systemctl status blocky
× blocky.service - Blocky DNS proxy
     Loaded: loaded (/etc/systemd/system/blocky.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Mon 2024-09-30 23:13:52 IST; 9min ago
   Duration: 3ms
    Process: 20397 ExecStart=/[PATH]/blocky --config /[PATH]/config.yml (code=exited, status=203/EXEC)
   Main PID: 20397 (code=exited, status=203/EXEC)
        CPU: 1ms

Sep 30 23:13:52 fedora systemd[1]: blocky.service: Scheduled restart job, restart counter is at 5.
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Start request repeated too quickly.
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:13:52 fedora systemd[1]: Failed to start blocky.service - Blocky DNS proxy.

$ cat config.yml
upstreams:
  groups:
    default:
      - https://cloudflare-dns.com/dns-query
      - https://dns.quad9.net/dns-query
      - 8.8.8.8

ports:
  dns: 53
  tls: 853
  https: 443
  http: 4000

bootstrapDns:
  - tcp+udp:1.1.1.1

blocking:
  denylists:
    ads:
      - https://big.oisd.nl/domainswild
      - "/home/[USERNAME]/Documents/Blocklists/News Wildcard.txt"
      - "/home/[USERNAME]/Documents/Blocklists/Social Media Wildcard.txt"
      - |
        *.google.com
  clientGroupsBlock:
    default:
      - ads
  blockType: nxDomain
  loading:
    refreshPeriod: 1h
    downloads:
      timeout: 5m
      attempts: 3
      cooldown: 2s


caching:
  minTime: 5m
  maxTime: 30m
  maxItemsCount: 0
  prefetching: true
  prefetchExpires: 24h
  prefetchThreshold: 2
  prefetchMaxItemsCount: 0

prometheus:
  enable: true
  path: /[PATH]/metrics

queryLog:
  type: csv
  target: /[PATH]/logs
  logRetentionDays: 7
  flushInterval: 30s

$ journalctl -u blocky -n 50 --no-pager
Sep 30 23:10:02 fedora systemd[1]: blocky.service: Scheduled restart job, restart counter is at 5.
Sep 30 23:10:02 fedora systemd[1]: blocky.service: Start request repeated too quickly.
Sep 30 23:10:02 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:10:02 fedora systemd[1]: Failed to start blocky.service - Blocky DNS proxy.
Sep 30 23:12:54 fedora systemd[1]: Started blocky.service - Blocky DNS proxy.
Sep 30 23:12:54 fedora systemd[1]: blocky.service: Main process exited, code=exited, status=203/EXEC
Sep 30 23:12:54 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:12:54 fedora systemd[1]: blocky.service: Scheduled restart job, restart counter is at 1.
Sep 30 23:12:54 fedora systemd[1]: Started blocky.service - Blocky DNS proxy.
Sep 30 23:12:54 fedora systemd[1]: blocky.service: Main process exited, code=exited, status=203/EXEC
Sep 30 23:12:54 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:12:54 fedora systemd[1]: blocky.service: Scheduled restart job, restart counter is at 2.
Sep 30 23:12:54 fedora systemd[1]: Started blocky.service - Blocky DNS proxy.
Sep 30 23:12:54 fedora systemd[1]: blocky.service: Main process exited, code=exited, status=203/EXEC
Sep 30 23:12:54 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:12:55 fedora systemd[1]: blocky.service: Scheduled restart job, restart counter is at 3.
Sep 30 23:12:55 fedora systemd[1]: Started blocky.service - Blocky DNS proxy.
Sep 30 23:12:55 fedora systemd[1]: blocky.service: Main process exited, code=exited, status=203/EXEC
Sep 30 23:12:55 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:12:55 fedora systemd[1]: blocky.service: Scheduled restart job, restart counter is at 4.
Sep 30 23:12:55 fedora systemd[1]: Started blocky.service - Blocky DNS proxy.
Sep 30 23:12:55 fedora systemd[1]: blocky.service: Main process exited, code=exited, status=203/EXEC
Sep 30 23:12:55 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:12:55 fedora systemd[1]: blocky.service: Scheduled restart job, restart counter is at 5.
Sep 30 23:12:55 fedora systemd[1]: blocky.service: Start request repeated too quickly.
Sep 30 23:12:55 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:12:55 fedora systemd[1]: Failed to start blocky.service - Blocky DNS proxy.
Sep 30 23:13:51 fedora systemd[1]: Started blocky.service - Blocky DNS proxy.
Sep 30 23:13:51 fedora systemd[1]: blocky.service: Main process exited, code=exited, status=203/EXEC
Sep 30 23:13:51 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:13:51 fedora systemd[1]: blocky.service: Scheduled restart job, restart counter is at 1.
Sep 30 23:13:51 fedora systemd[1]: Started blocky.service - Blocky DNS proxy.
Sep 30 23:13:51 fedora systemd[1]: blocky.service: Main process exited, code=exited, status=203/EXEC
Sep 30 23:13:51 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Scheduled restart job, restart counter is at 2.
Sep 30 23:13:52 fedora systemd[1]: Started blocky.service - Blocky DNS proxy.
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Main process exited, code=exited, status=203/EXEC
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Scheduled restart job, restart counter is at 3.
Sep 30 23:13:52 fedora systemd[1]: Started blocky.service - Blocky DNS proxy.
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Main process exited, code=exited, status=203/EXEC
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Scheduled restart job, restart counter is at 4.
Sep 30 23:13:52 fedora systemd[1]: Started blocky.service - Blocky DNS proxy.
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Main process exited, code=exited, status=203/EXEC
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Scheduled restart job, restart counter is at 5.
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Start request repeated too quickly.
Sep 30 23:13:52 fedora systemd[1]: blocky.service: Failed with result 'exit-code'.
Sep 30 23:13:52 fedora systemd[1]: Failed to start blocky.service - Blocky DNS proxy.
ThinkChaos commented

Creating a service that works to provide your system DNS is harder than normal services because it has to start much earlier.
Look at how systemd-resolvd's service works.

ChitranshuV commented

Can there be a feature for auto-start on boot in the future releases?

ThinkChaos commented

I don't think it's possible for Blocky to do that, nor really in scope, as you see setting it up to run on startup is highly context dependent and the job of the service manager.
If you use the container there's usually a way to get it to auto start, though that won't solve the issue of it not being properly integrated with Systemd targets and other services.

  • 👍1
ChitranshuV commented

I ended up creating an alias in ~/.bashrc to launch it quickly from any directory, and I also used the 'Startup Applications' feature in Cinnamon DE to create an autostart job at boot. Just writing the execution command there was enough.

  • 👍1
ChitranshuV commented

I figured out my mistake in creating systemd service. Replying for future users.. This works pretty good.

$ cat /etc/systemd/system/blocky.service
[Unit]
Description=Blocky
After=network-online.target
Wants=network-online.target

[Service]
ExecStart=/bin/bash -c "/home/chitranshu/Downloads/blocky_v0.24_Linux_x86_64/blocky --config /home/chitranshu/Downloads/blocky_v0.24_Linux_x86_64/config.yml"
Restart=always
RestartSec=10
User=beforesunset

[Install]
WantedBy=multi-user.target
  • ❤️1