Pi 4 - Buster - Pihole V5.1.2 - Random 'DNS Service Not Running' issues - Using Unbound

[RFBomb]

Please follow the below template, it will help us to help you!

FYI I am using UNBOUND on this device. I'm not sure if the problem is relayed to that, but I followed the documentation to get it working with pihole, and that appears to be working properly. The issue is that the pihole reports that the DNS service and FTL both stop running.

• Pi-hole [v5.1.2]
• Web Interface [v5.1.1]
• FTL [v5.2]

Expected Behaviour:

DNS / FTL service runs without issue.

Actual Behaviour:

DNS service / FTL randomly stops running.

Last time I had to resort to reinstalling pihole on the device to fix it. And before I could do that, I had to disable unbound and change the PI's DNS servers. After doing that, I was able to reinstall pihole, re-enable unbound (by commenting out the hardcoded DNS server) and everything was functional again.

This time, I followed this page's instructions and it was resolved.

DNS Service not running

Your debug log shows that piHole-FTL is not running: *** [ DIAGNOSING ]: Ports in use *:80 lighttpd (IPv4) *:80 lighttpd (IPv6) *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain [✗] Failed to resolve fili.tv via localhost (127.0.0.1) [✗] Failed to resolve fili.tv via Pi-hole (10.0.69.22) [✓] doubleclick.com is 108.177.112.113 via a remote, public DNS server (8.8.8.8) Try running this command to restart FTL. sudo service pihole-FTL restart …

Specifically this command resolved it: sudo service pihole-FTL restart
I then ran this just in case: pihole checkout master (Note that it told me I was converting from the master branch to the master branch.)

While this issue has been resolved for now, I'm confused as to why it keeps cropping up? I've fixed it 3 times now I think. This time it was fairly easy, but I don't understand why its happening when it never had such an issue on my pi3.

Debug Token:

https://tricorder.pi-hole.net/yxitvm3bgy

[Bucking_Horn]

Your debug log provides no immediate hints towards your issue, as it shows both pihole-FTL and lighttpd as running:

*** [ DIAGNOSING ]: Pi-hole processes
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

The following two commands may yield more information, especially when executed immediately after your issue reoccurs:

sudo systemctl status --full --no-pager pihole-FTL.service

sudo systemctl status --full --no-pager lighttpd.service

[RFBomb]

Next time it occurs I’ll try those and report back. Thanks. I just wanted to bring light that There is an issue is all. I understand that having posted a log where it was working is of no use lol