I've seen several topics discussing the "getOverTimeID" error and thought I would share what I found.
On my system, I was seeing this error in /var/log/pihole-FTL.log for every DNS query that came in. Checking my /etc/rc2.d startups, S02pihole-FTL was starting IMMEDIATELY after S02ntp, but a fraction of a second BEFORE NTP had updated the system time. So, when pihole-FTL starts, it thinks it's December 31, 1969 @ 18:00 (in my timezone). Then NTP fast-forwards the date by 51 years and pihole-FTL is not happy about it.
So, the fix for me was to add a "sleep 2" in the /etc/init.d/pihole-FTL startup script, above the "if setcap CAP_NET_BIND_SERVICE...." line, in the start() section.
Hopefully this helps somebody else.