WARN: getOverTimeID(1586318700): 1050 is too large: 1585688700

[Bewright]

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

Expected Behaviour:

[Expect there shouldn't be this entry in the logs. Otherwise everything else appears to be functioning correctly.]

Actual Behaviour:

_[the debug log has the following multiple entries as well as the Tail pi-hole-FTL.log WARN: getOverTimeID(1586318700): 1050 is too large: 1585688700

I've done searches and could find no clear answer to this issue, checked the timedate
pi@raspberrypi:~ $ timedatectl status
Local time: Wed 2020-04-08 09:55:08 EDT
Universal time: Wed 2020-04-08 13:55:08 UTC
RTC time: n/a
Time zone: America/Toronto (EDT, -0400)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
it is accurate._

Debug Token:

[1ud6e46vj6]

[jfb]

This post reference at the bottom of this reply may have information of interest. If you take a look at one entry in your log, where the times are shown in epoch time:

[2020-04-08 00:00:09.812 957] WARN: getOverTimeID(1586318700): 1050 is too large: 1585688700

Pi-hole has recorded a query for

date -d @1585688700
Tue 31 Mar 2020 04:05:00 PM CDT (this is UTC-5 in summer, so UTC would be 09:05:00 PM)

and Pi-hole thinks the current time is:

date -d @1586318700
Tue 07 Apr 2020 11:05:00 PM CDT (or Wed 08 Apr 2020 04:05:00 AM UTC)

This is usually due to a time upset on the Pi-hole host. You can check journalctl -u systemd-timesyncd.service for details of time events.

[Bewright]

Thanks for the quick reply. I believe the timing issue is resolved. The link appears to be dead.

[jfb]

Apologies for the bad link. Removed in my reply.