I'm running Pi-hole on a Raspberry Pi 4B with Raspberry Pi OS – Debian GNU/Linux 12 (bookworm).
Whenever I restart the pi, I get this message in Pi-hole diagnoses:
2024-10-02 14:51:57 NTP Error in NTP client: Cannot resolve NTP server address: Try again
The system uses systemd-timesyncd and this is the output from journalctl:
Oct 02 14:51:25 pi-hole systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
░░ Subject: A start job for unit systemd-timesyncd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit systemd-timesyncd.service has begun execution.
░░
░░ The job identifier is 17.
Oct 02 14:51:25 pi-hole systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization.
░░ Subject: A start job for unit systemd-timesyncd.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit systemd-timesyncd.service has finished successfully.
░░
░░ The job identifier is 17.
Oct 02 14:52:18 pi-hole systemd-timesyncd[360]: Contacted time server 129.250.35.250:123 (2.debian.pool.ntp.org).
Oct 02 14:52:18 pi-hole systemd-timesyncd[360]: Initial clock synchronization to Wed 2024-10-02 14:52:18.824212 CEST.
░░ Subject: Initial clock synchronization
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ For the first time during the current boot an NTP synchronization has been
░░ acquired and the local system clock adjustment has been initiated.
So it seems that FTL tries to sync the time before the service has successfully launched.
I disabled: ntp.sync.active since the systemd service takes care of this, and the error doesn't show up anymore. But is there a way to delay FTL's first sync attempted?