Hi,
Having Pi-hole on two Pi4s.
Both runs the latest Beta v6.
One handle the wired network and the other the wireless network.
Today after running pihole -up and a reboot of both, the one handling the wireless network showed under diagnostics Standard deviation of time offset is too large, rejecting synchronization
Tried a couple of reboots, still same message.
The date command shows same time as on the other Pi-hole installation and so does the command timedatectl status.
NTP settings are the same on both = standard.
Had a look at the output from pihole -d which for me looks ok.
Ahh yes you are right, my bad using "error" I should as you correctly point out have used "warning" I have changed the subject line.
Anyway, why suddenly I see this?
I have been using Beta 6 more or less since Beta test was started and never before seen this warning, on the same two Raspberry PI4s?
I have checked all settings on both Raspberries all same same, just they sits on two different subnets.
The command systemctl status systemd-timesyncd shows same result on the two Raspberries.
Output from both is as close as the difference between I issue the command on both.
I think all should be fine, the warning is not popping up very frequent.
Pi4-1
Local time: Sun 2024-09-22 09:35:16 IST
Universal time: Sun 2024-09-22 08:35:16 UTC
RTC time: n/a
Time zone: Europe/Dublin (IST, +0100)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
Pi4-2
Local time: Sun 2024-09-22 09:35:18 IST
Universal time: Sun 2024-09-22 08:35:18 UTC
RTC time: n/a
Time zone: Europe/Dublin (IST, +0100)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no