Normal PiHole beavior...
DNS service not running and webinterface shows "No connection to API"
can't upload debug protokoll
I did simply run pihole -up to update from lastest version at that time to the version 4.3. That's all.
After several hours DNS service stops running and webinterface shows "No connection to API". With an reboot of the pi I can solve the problem for some hours.
Any clue?
Thanks George
Tried to relaunch the service ?
Yes, by sudo reboot the pi. However next day same error.
George
This will temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.
sudo nano /etc/resolv.conf
edit nameserver 127.0.0.1 to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit
Run pihole -d and upload the debug log
Hi jfb, my setting is that pi-hole is named as local dns (having a fritzbox) and all clients request pi-hole. within pi-hole custom dns is my fritzbox. Fritzbox has 9.9.9.9 as default DNS.
Even is this setting I should do what you stated above?
I would say this could be a solution when pi-hole is actively "asking" a upstream DNS like 9.9.9.9. But my pi-hole is asking my router and router sends it to upstream DNS. Or am I wrong?
Thanks!
BTW: There is an error while trying to upload the debgug log. Cannot upload it.
What is the output of:
sudo systemctl status pihole-FTL.service
Yes. The Pi is using the DNS server specified in the resolv.conf file, which is likely not the router. It is usually 127.0.0.1 (the loopback address for the Pi), which leads it to the Pi-Hole.
CGroup: /system.slice/pihole-FTL.service
output of:
sudo systemctl status pihole-FTL.service
May 22 18:12:37 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
May 22 18:12:37 raspberrypi pihole-FTL[24862]: Not running
May 22 18:12:37 raspberrypi su[24904]: Successful su for pihole by root
lines 1-11/15 70%
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Wed 2019-05-22 18:12:37 CEST; 50min ago
Docs: man:systemd-sysv-generator(8)
Process: 24808 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 24862 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/pihole-FTL.service
lines 1-8/15 49%...skipping...
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generate
Active: active (exited) since Wed 2019-05-22 18:
Docs: man:systemd-sysv-generator(8)
Process: 24808 ExecStop=/etc/init.d/pihole-FTL st
Process: 24862 ExecStart=/etc/init.d/pihole-FTL s
CGroup: /system.slice/pihole-FTL.service
May 22 18:12:37 raspberrypi systemd[1]: Starting LS
May 22 18:12:37 raspberrypi pihole-FTL[24862]: Not
May 22 18:12:37 raspberrypi su[24904]: Successful s
May 22 18:12:37 raspberrypi su[24904]: + ??? root:p
May 22 18:12:37 raspberrypi su[24904]: pam_unix(su:
May 22 18:12:37 raspberrypi pihole-FTL[24862]: FTL
May 22 18:12:37 raspberrypi systemd[1]: Started LSB
~
~
~
I did that following pihole -r
This output is stripped and it's missing information, can you run it again and paste all the information ?
sudo systemctl status --full --no-pager pihole-FTL.service
Thx Dan see below:
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Wed 2019-05-22 18:12:37 CEST; 1h 15min ago
Docs: man:systemd-sysv-generator(8)
Process: 24808 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 24862 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/pihole-FTL.service
May 22 18:12:37 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
May 22 18:12:37 raspberrypi pihole-FTL[24862]: Not running
May 22 18:12:37 raspberrypi su[24904]: Successful su for pihole by root
May 22 18:12:37 raspberrypi su[24904]: + ??? root:pihole
May 22 18:12:37 raspberrypi su[24904]: pam_unix(su:session): session opened for user pihole by (uid=0)
May 22 18:12:37 raspberrypi pihole-FTL[24862]: FTL started!
May 22 18:12:37 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
pihole status says:
pi@raspberrypi:~ $ pihole status
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled
Looks like the resolver is working properly ...
what about
nslookup google.com
nslookup google.com 1.1.1.1
Hi, thanks for your help!
nslookups google.com says: Server: 127.0.01 Address: 127.0.0.1#53
and non-authorative answer: google.com adress 216.58.206.14
google.com 1.1.1.1 says Server: 1.1.1.1 Address: 1.1.1.1#53
and non-answer: google.com and 172.217.19.110
Sounds like your Pi-hole is up and running ...
Still seeing the error on the admin interface ?
no, after a rebbot of the pi all was fine. first api error was yesterday at noon. did reboot pi - next api error was hours later today in the morning.
I did today after I saw the error again sudo nano /etc/resolv.conf edit nameserver 127.0.0.1 to nameserver 9.9.9.9 and then pihole -r.
When you see the error again, please run the
sudo systemctl status --full --no-pager pihole-FTL.service
command and post the results.
We cannot troubleshoot it now as it's up and running with out any errors ...
I'll do! Many thanks for your support!
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.