@Bucking_Horn of @deHakkelaar 's suggestions, the only one it could possible be is running out of memory. I'm using the power adapter that came with the Canakit starter pack, which should mean no under voltage. The Pihole doesn't need a reboot, I just have to tell the router to use default dns for a few minutes, then point it back again. Finally, the Pihole is connected by ethernet.
And I wouldnt rule out the power adapter or cable just bc it came in a kit.
The power adapter or cable could be DOA/DFS or just a cheap one not able to do the job.
(Dead On Arrival / Defect From Stock)
That same kernel ring buffer can be checked for "under-voltage" messages:
dmesg -T | grep -i voltage
Or checking the logs stored on the SD card that go longer back (the kernel ring buffer stored in RAM gets wiped on reboot):
zgrep -ni voltage /var/log/syslog.*
And I wouldnt rule out filesystem errors caused by power outage or insufficient or unstable power:
@deHakkelaar The voltage checks did not return anything, and I didn't see anything like what you posted for the oom killer, although I noticed that when it cut out this morning the dashboard showed the attached pattern of activity.
But not sure if any results gets logged with above.
Better connect a display to the Pi to see boot sequence.
That screenshot you posted doesnt show the vertical Y axes making it impossible to see how many queries.
Did you check who made all those queries via the web GUI or checking the logs with below ?
less -p 'Oct 8 02:00:00' /var/log/pihole.log
Above one makes me suspect you have configured a DNS loop somewhere.
What upstream DNS server(s) is/are configure on Pi-hole ?
sudo grep server= -R /etc/dnsmasq.*
And what DNS server(s) is/are configured on the router in the WAN/Internet section ?
The query log shown on the dashboard does not go back more than 24 hours, but the long-term data tab on the browser will allow you to see all the queries made for the past 365 days (or when Pi-hole was installed, whichever is shorter).
@jfb@deHakkelaar ok, having now upped my php memory to 1350 M, it looks like the biggest query creator on Oct. 8 was my desktop (61232), followed by my laptop (57153), my wife's phone (49344), my smart display (45283), my daughter's smart speaker (43106), my smart speakers (42927), office speaker (35395), my tablet (34971), the bedroom smart display (27112), and my phone (23733).
@deHakkelaar, I'm sorry, you're right. I did change it after I realized that it was easier to see activity if the pihole was providing ip addresses, so I disabled DHCP on the router and enabled it on the pihole.
However, I continue to get the timeout.
To check the /boot partition, I need to remove SD card and plug it into my desktop?
That was the initial idea yeah ... if you were to check the other EXT4 partition on another PC at same time anyway.
Dont need to to do that now.
The /boot partition/mount is only invoked at boot time so after the system comes up, that /boot partition is not involved anymore.
If you want to check anyway (without the desktop PC), make sure no processes have files open on that /boot mount:
pi@ph5:~ $ sudo lsof /boot/
pi@ph5:~ $
Unmount the filesystem:
pi@ph5:~ $ sudo umount /boot
pi@ph5:~ $
And run fsck (with auto repair argument) on the partition:
When the timeouts occure, are you still able to ping and SSH into the Pi ?
If so, it could be the configured upstream DNS servers causing troubles somehow.
Try do below two when have problems again and post results here:
nslookup pi-hole.net 1.1.1.1
nslookup pi-hole.net 1.0.0.1
And when have another PC running Windows, Linux or MacOS, run above same two commands on them in a command prompt too.
You seem to have intermittent problems with your Internet connection.
This is not really Pi-hole related.
Run below one on Pi-hole when everything is working and when not working (timeouts) to compare:
traceroute -n 1.1.1.1
Same for the Windows machine:
tracert -d 1.1.1.1
And depending results, report an issue at your ISP.
Not solved, but it seems we're at an impasse if it's not pi-hole related! I can't get my ISP to come out and do anything about it as long as covid is as bad as it is in my area.
Did the problem arise again and did you do the tracert on the Windows box ?
If that tracert cuts short at some IP, thats where the problem lies.
And as this is all IP/ICMP based (no DNS), Pi-hole isn't involved.