Expected Behaviour:
It should list the queries.
Actual Behaviour:
Error popup. See screenshot.
(also of note, the word "occured" is misspelled in the error message, the correct spelling is "occurred")
Is this bare metal or virtualized?
What is the contents of /etc/dnsmasq.conf? Something is preventing Pi-hole from being able to use its own hostname.
May 8 00:00:01 dnsmasq[640]: query[A] pi.hole from 127.0.0.1
May 8 00:00:01 dnsmasq[640]: forwarded pi.hole to 192.168.2.1
May 8 00:00:01 dnsmasq[640]: forwarded pi.hole to 192.168.2.1
May 8 00:00:01 dnsmasq[640]: validation pi.hole is BOGUS
May 8 00:00:01 dnsmasq[640]: reply error is SERVFAIL
-rwxr-xr-x 1 root root 44 May 8 19:04 /etc/pihole/local.list
192.168.1.225 Pi-hole
192.168.1.225 pi.hole
*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
-rwxr-xr-x 1 root root 1714 May 8 19:10 /etc/dnsmasq.d/01-pihole.conf
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=10000
log-queries
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=192.168.2.1
domain-needed
bogus-priv
dnssec
trust-anchor=.,19036,8,2,49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5
trust-anchor=.,20326,8,2,E06D44B80B8F1D39A95C0B0D7C65D08458E880409BBC683457104237C7F8EC8D
except-interface=nonexisting
server=/home.lan/192.168.1.1
server=/1.168.192.in-addr.arpa/192.168.1.1
server=/use-application-dns.net/
Leads to:
2020-05-03 21:29:45: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 46
2020-05-03 21:29:45: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 47
2020-05-03 21:29:45: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 52
This is also of concern:
[2020-05-08 19:10:29.931 920] *************************************************************************
[2020-05-08 19:10:29.931 920] * WARNING: Required Linux capability CAP_NET_ADMIN not available *
[2020-05-08 19:10:29.931 920] *************************************************************************
[2020-05-08 19:10:30.006 920] PID of FTL process: 920
[2020-05-08 19:10:30.006 920] Listening on port 4711 for incoming IPv4 telnet connections
[2020-05-08 19:10:30.007 920] Listening on Unix socket
[2020-05-08 19:10:30.007 920] Received SIGHUP, reloading cache
[2020-05-08 19:10:30.007 920] Blocking status is enabled
This is virtualized. Apologies for lack of those details, I wasn't sure if the debug token made that obvious.
Pi-hole running in a docker container on Synology.
The contents of the debug log are in the /var/log directory, you can see exactly what we see, you may find some other information there that is helpful.
I am running pi-hole, with Cloudflared upstream DNS. Nothing unusual afaik, it "sometimes" works in displaying the queries, but sometimes I get that error. This has started recently, but I just restarted the pi-hole container and it worked for a few minutes, then I get the error again. I just went back and it was working again. It appears to be intermittent, but when it doesn't work, it is instantaneous, it's not like a timeout at all, the error pops up instantly.
My /etc/dnsmasq.conf is:
conf-dir=/etc/dnsmasq.d
user=root
File: 01-pihole.conf
# Pi-hole: A black hole for Internet advertisements
# (c) 2017 Pi-hole, LLC (https://pi-hole.net)
# Network-wide ad blocking via your own hardware.
#
# Dnsmasq config for Pi-hole's FTLDNS
#
# This file is copyright under the latest version of the EUPL.
# Please see LICENSE file for your rights under this license.
###############################################################################
# FILE AUTOMATICALLY POPULATED BY PI-HOLE INSTALL/UPDATE PROCEDURE. #
# ANY CHANGES MADE TO THIS FILE AFTER INSTALL WILL BE LOST ON THE NEXT UPDATE #
# #
# IF YOU WISH TO CHANGE THE UPSTREAM SERVERS, CHANGE THEM IN: #
# /etc/pihole/setupVars.conf #
# #
# ANY OTHER CHANGES SHOULD BE MADE IN A SEPARATE CONFIG FILE #
# WITHIN /etc/dnsmasq.d/yourname.conf #
###############################################################################
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=10000
log-queries
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=192.168.2.1#5054
domain-needed
bogus-priv
dnssec
trust-anchor=.,19036,8,2,49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5
trust-anchor=.,20326,8,2,E06D44B80B8F1D39A95C0B0D7C65D08458E880409BBC683457104237C7F8EC8D
local-service
server=/home.lan/192.168.1.1
server=/1.168.192.in-addr.arpa/192.168.1.1
server=/use-application-dns.net/
File: 10-subnet-dns.conf
server=/0.0.10.in-addr.arpa/192.168.1.1
Everything looks okay with those config lines. What is a problem is that you have pi.hole defined in /etc/pihole/local.list as 192.168.1.225. But the IP address on the PI-hole network interface is 192.168.2.2. I think you have renumbered your network and half of the configs are set to 192.168.1.0 while others are 192.168.2.0.
It's so strange, this was working for almost a week before I started getting that error.
I have set up the networking with a Bridge so my other containers / Synology can also access Pi-hole. And I send the request to Cloudflared at 192.168.2.1#5054.
So, requests from Synology / other containers come into pi-hole on 192.168.2.2; requests from other devices on the LAN come in at 192.168.1.225.
Of note, the flag "Listen on all interfaces, permit all origins" never persists on restart. If I have to reboot pi-hole, I have to go in and re-select that each time. (not sure if that behavior is pertinent)
https://dl.dropboxusercontent.com/s/sy6axl7f5jckliz/example_error.gif?dl=0(image larger than 8192KB)
here is an example of it working just fine, then it stopping for some reason.
Just a wild ballpark guess but it's likely something to do with routing or permissions.
The debug log shows:
-rw-r--r-- 1 www-data www-data 6640 May 8 19:21 /var/log/lighttpd/error.log
2020-05-03 21:25:23: (log.c.217) server started
2020-05-03 21:26:32: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 46
2020-05-03 21:26:32: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 47
2020-05-03 21:26:32: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 52
2020-05-03 21:26:50: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 46
2020-05-03 21:26:50: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 47
2020-05-03 21:26:50: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 52
2020-05-03 21:27:02: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 46
2020-05-03 21:27:02: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 47
2020-05-03 21:27:02: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 52
2020-05-03 21:28:52: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 46
2020-05-03 21:28:52: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 47
2020-05-03 21:28:52: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 52
2020-05-03 21:29:19: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 46
2020-05-03 21:29:19: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 47
2020-05-03 21:29:19: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 52
2020-05-03 21:29:36: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 46
2020-05-03 21:29:36: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 47
2020-05-03 21:29:36: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 52
2020-05-03 21:29:41: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 46
2020-05-03 21:29:41: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 47
2020-05-03 21:29:41: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 52
2020-05-03 21:29:45: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 46
2020-05-03 21:29:45: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 47
2020-05-03 21:29:45: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined offset: 2 in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 52
It may be that the web interface is trying to get the current version for the footer display and something is getting mixed in the process. @PromoFaux might have some insight on that.
What can help in the meantime is to watch /var/log/lighttpd/access.log and /var/log/lighttpd/error.log in real time when this interface issue happens. It may also be related to the memory allocation for php, the default is 128M and the query log will blow through that if there's a large history.
Lastly, if Listen All Interfaces is not sticky then /etc/dnsmasq.d/01-pihole.conf is not persisting, check the file contents before you change Listen All and then diff that with what the file reads after Listen All. If you reboot and the changes are not kept then you'll need to investigate why that file is being reset.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.