Please follow the below template, it will help us to help you!
Expected Behaviour:
pihole restartdns should restart FTLDNS
Actual Behaviour:
user@pi-hole:~ # pihole status
[✗] DNS service is NOT running
user@pi-hole:~ # pihole restartdns
[✓] Starting DNS service
user@pi-hole:~ # pihole status
[✗] DNS service is NOT running
user@pi-hole:~ #
Debug Token:
Generate Debug fails to create and upload a debug token, until reboot...
This is a post reboot log
Your debug token is: https://tricorder.pi-hole.net/vi2yl1b4hv
I noticed the behavior when trying to install 1) Cloudflared DoH client and then 2) Unbound. Which is when I realized the problem probably existed prior to installing either of these.
It's weird... I did another pihole restartdns and waited like 3 minutes. Same. Pihole-FTL is not running.
It starts in less than 3 minutes after a reboot after the desktop (raspbian) appears. So I stopped it deliberately. Using service pihole stop. Then confirmed DNS service is stopped and tried to restart. Same. This time after waiting 10 minutes. So it looks like manual restarts/starts are failing.
There was a line in the logs that referenced "/" was not found on the line pihole/index.php. It spit that out like three times. I made an edit to the /etc/lighttpd/lighttpd.conf and added a line that had that in it. as requested by [PiPass]. But it didn't work so I backed out all the changes and removed that line from the conf. So I am not sure why that error is appearing in the logs anymore.
What does sudo systemctl status --full --no-pager pihole-FTL.service say when you do a manual restart? And what does the /var/log/pihole-FTL.log show for the current session?
The lighttpd issue is something unrelated and has to do with Buster.
Let me emphasis that it starts normally on reboot. I am making a change to the upstream DNS server in the settings page of the console and attempting to restart to cement the new settings into place and its failing.
A reboot will start the service even with the new setting [setting to enable Unbound] in effect but Unbound isn't working so I am making more changes and attempting to restart the service, and it fails again. So this behavior is leading me to believe there is some other underlying problem.