pihole-FTL not started at boot

Help
1

Expected Behaviour:

  • Debian GNU/Linux 11 (bullseye)
  • Raspberry Pi 5

After a reboot, pihole-FTL should start, and pihole status should indicated that blocking is enabled.

Actual Behaviour:

pihole-FTL is not started. pihole status indicates that DNS is not running. Starting pihole-FTL manually corrects the problem.

root@pihole:~# pihole status
  [✗] DNS service is NOT running
root@pihole:~# systemctl status pihole-FTL
● pihole-FTL.service - Pi-hole FTL
     Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
root@pihole:~# systemctl start pihole-FTL
root@pihole:~# pihole status
  [✓] FTL is listening on port 53
     [✓] UDP (IPv4)
     [✓] TCP (IPv4)
     [✓] UDP (IPv6)
     [✓] TCP (IPv6)

  [✓] Pi-hole blocking is enabled

Debug Token:

https://tricorder.pi-hole.net/8euNPnwg/

2

I found the problem. journalctl showed that there was a cycle in the service dependencies that was preventing pihole-FTL from starting. I found the service that was causing it and disabled it. Now it is working as expected.

journalctl -b | grep FTL
May 08 17:38:30 pihole systemd[1]: multi-user.target: Found ordering cycle on pihole-FTL.service/start
May 08 17:38:30 pihole systemd[1]: multi-user.target: Job pihole-FTL.service/start deleted to break ordering cycle starting with multi-user.target/start
3

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.