Time not syncing on startup - RPi 4

asd78 · June 8, 2024 at 7:29 PM

I have just installed libreelec on a raspberry pi 4, hooked up to a tv. I have been through all the settings, so that I have a setup I like. This of course includes the NTP server setup.
Every time the Pi is turned on, the clock says 18:27. This makes sense, since the Pi doesn't have a CMOS to keep time when powered off. The Pi does however not correct the time under startup. If I manually go into the libreelec settings -> connections -> NTP and then save the settings, the clock updates immediatly.

The raspberry is querying the local firewall for network time.
Here is my debug log:
https://paste.libreelec.tv/one-elf.log

As far as I can tell, the NTP server isn't queried once under startup. First when I change the settings manually.

Any idea to what is causing this?

**chewitt** · June 9, 2024 at 5:16 AM

Code

Feb 27 18:26:11.509638 INTSVC-STREAMPI connmand[575]: Skipping server 172.21.21.254 KoD code RATE
..
Feb 27 18:26:25.768188 INTSVC-STREAMPI connmand[575]: Skipping server 172.21.21.254 KoD code RATE
..
Feb 27 18:26:39.762246 INTSVC-STREAMPI connmand[575]: Skipping server 172.21.21.254 KoD code RATE
..
Feb 27 18:27:01.976455 INTSVC-STREAMPI connmand[575]: ntp: adjust (jump): +8815445.461668 sec
Jun 08 20:11:07.439421 INTSVC-STREAMPI connmand[575]: eth0 {add} route 82.165.8.211 gw 172.21.21.254 scope 0 <UNIVERSE>
..
Jun 08 20:11:07.499950 INTSVC-STREAMPI connmand[575]: Skipping server 172.21.21.254 KoD code RATE
..
Jun 08 20:11:22.227952 INTSVC-STREAMPI connmand[575]: Skipping server 172.21.21.254 KoD code RATE
Jun 08 20:11:36.227660 INTSVC-STREAMPI connmand[575]: Skipping server 172.21.21.254 KoD code RATE
Jun 08 20:12:05.538565 INTSVC-STREAMPI crond[438]: time disparity of 146925 minutes detected

Display More

(re)configure your NTP server to stop sending Kiss of Death (KoD) responses when we attempt to sync against it and we'll manage to reset the time much earlier in the boot sequence. Or just leave NTP unconfigured and we'll default to pool.ntp.org servers which normally work fine for people.

asd78 · June 9, 2024 at 7:48 PM

Quote from chewitt

(re)configure your NTP server to stop sending Kiss of Death (KoD) responses when we attempt to sync against it and we'll manage to reset the time much earlier in the boot sequence. Or just leave NTP unconfigured and we'll default to pool.ntp.org servers which normally work fine for people.

I swear to god I have looked through that log multiple times. You are a godsend. I will reconfigure the NTP server. Thanks a bunch!

Time not syncing on startup - RPi 4

Similar Threads

Problem booting LE 11.95 on Raspberry Pi 4 and 5

How to automatically change resolution after switching TVs?

LibreELEC (Omega) 12 Beta2