Pi-hole becomes unresponsive after few days

Help
1

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

Expected Behaviour:

Works beautifully

Actual Behaviour:

Works beautifully for a few days then becomes slow, Cannot access via web or ssh

Debug Token:

run 11 hours after reboot
https://tricorder.pi-hole.net/bin7x8y4pv

Looks like pihole-FTL.log
becomes swamped with error messages of type
WARN: getOverTimeID(1571007900): 486 is too large: 1570716300

I have seen this reported elsewhere but cannot see any recorded answer to fix.

Thanks, David

2

I should have added that date and time on Pi are correct

3

Edit - removed incorrect information here

What is the output of this command from the Pi Terminal:

echo ">stats" | nc localhost 4711

4

Query volume was not high. result of requested command is;-

pi@raspberrypi:~ $ echo ">stats" | nc localhost 4711
domains_being_blocked 113448
dns_queries_today 5743
ads_blocked_today 401
ads_percentage_today 6.982413
unique_domains 743
queries_forwarded 2088
queries_cached 3252
clients_ever_seen 11
unique_clients 10
dns_queries_all_types 5743
reply_NODATA 1488
reply_NXDOMAIN 134
reply_CNAME 1426
reply_IP 2623
privacy_level 0
status enabled
---EOM---
5

I don't think my previous reply was accurate (working off mobile). The getOverTime message normally indicates that the time on the Pi was recently changed. I'll ask one of the developers to look at this.

7

Other logs to look for errors:

journalctl -u systemd-timesyncd.service

journalctl -u ntp

journalctl

less /var/log/syslog

dmesg | less

8 
journalctl -u systemd-timesyncd.service

-- Logs begin at Fri 2019-10-11 15:17:01 BST, end at Mon 2019-10-14 22:50:02 BST. --

Oct 11 15:17:14 raspberrypi systemd[1]: Starting Network Time Synchronization...

Oct 11 15:17:16 raspberrypi systemd-timesyncd[206]: System clock time unset or jumped backwards, restoring from recorded timestamp: Fri 2019-10-11 15:33:52 BST

Oct 11 15:33:52 raspberrypi systemd[1]: Started Network Time Synchronization.

Oct 13 23:27:44 raspberrypi systemd-timesyncd[206]: Synchronized to time server for the first time 203.95.213.129:123 (2.debian.pool.ntp.org).

~

~

`pi@raspberrypi:~ $ journalctl -u ntp`

-- Logs begin at Fri 2019-10-11 15:17:01
BST, end at Mon 2019-10-14 23:00:02 BST. --
-- No entries --
9 
pi@raspberrypi:~ $ timedatectl status
               Local time: Mon 2019-10-14 23:29:04 BST
           Universal time: Mon 2019-10-14 22:29:04 UTC
                 RTC time: n/a
                Time zone: Europe/London (BST, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no
12

Under ssh I reran raspi-config and reset the locale and then the timezone (No actual changes) then sudo reboot
Seems to be OK now, certainly no warnings of the getOverTimeID type.

Will keep a watch.

13

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.