Could this be the same issue as in the previous thread?
I started seeing this on Debian 12 and DietPi
Time Type Message
2024-07-10 14:51:42 NTP Error in NTP client:
Cannot resolve NTP server address: Unrecognized service
pihole -v
Core
Version is v5.17.3-403-g8b324741 (Latest: null)
Branch is development-v6
Hash is 8b324741 (Latest: 8b324741)
Web
Version is v5.19-820-g60ca1c7c (Latest: null)
Branch is development-v6
Hash is 60ca1c7c (Latest: 60ca1c7c)
FTL
Version is vDev-5c97d29 (Latest: null)
Branch is development-v6
Hash is 5c97d290 (Latest: 5c97d290)
cat /etc/debian_version
12.1
Let me know of I should check out a different branch
|NTP|Error in NTP client:
Failed to adjust time during NTP sync: Insufficient permissions|
pihole -v
Core
Version is v5.18.2-391-gb22731c6 (Latest: null)
Branch is development-v6
Hash is b22731c6 (Latest: b22731c6)
Web
Version is v5.19-822-g9d8a3dfc (Latest: null)
Branch is development-v6
Hash is 9d8a3dfc (Latest: 9d8a3dfc)
FTL
Version is vDev-c29e87d (Latest: null)
Branch is development-v6
Hash is c29e87df (Latest: c29e87df)
pihole -v
Core
Version is v5.18.2-391-gb22731c6 (Latest: null)
Branch is development-v6
Hash is b22731c6 (Latest: b22731c6)
Web
Version is v5.19-822-g9d8a3dfc (Latest: null)
Branch is development-v6
Hash is 9d8a3dfc (Latest: 9d8a3dfc)
FTL
Version is vDev-c29e87d (Latest: null)
Branch is development-v6
Hash is c29e87df (Latest: c29e87df)
root@CT108:~# pihole-FTL --config ntp
ntp.ipv4.active = true
ntp.ipv4.address =
ntp.ipv6.active = true
ntp.ipv6.address =
ntp.sync.server = pool.ntp.org
ntp.sync.interval = 3600
ntp.sync.count = 8
ntp.rtc.set = true
ntp.rtc.device =
ntp.rtc.utc = true
The two options you disabled are for offering time for synchronization not for doing the synchronization itself.
This is a different issue altogether, I suppose you are running your Pi-hole in some container? The only other way you could have no permissions I can come up with right now is an outdated core version.
Please update to the latest development-v6 version. You will find a new option ntp.sync.active which you can easily set to false to prevent any syncing from happening.