Connected but no date and nothing works

eungenue · July 26, 2020 at 10:38 PM

Hi all,

I've been struggling with date problem. It starts, connects to LAN/Wifi but nothing works. Date is wrong and displayed as Apr 2019.

Changing date from cmdline fixes the problem but obviously doesnt survive the reboot.

Checked ntp availability/firewall - everything works as expected. IPv6 doesn't seem to be configured on router.

I can see this in systemd log:

Apr 11 19:28:37 kodi1 systemd[1]: Condition check resulted in Network Time Synchronization being skipped.

but I can't think of anything that I could do to it.

connmand doesn't try to sync the time according to the logs.

No manually configured ntp servers are set in the GUI.

Read tons of time-related posts/solutions but nothing seems to be helpful.

Any suggestions are much appreciated.

LibreELEC 9.2.1 (i've tried latest 9.2.3 but that made no difference)

http://ix.io/2sob

http://ix.io/2soc

**Klojum** · July 27, 2020 at 12:52 AM Official Post

Any chance you have forgotten to enable the "Wait for network" option in the LibreELEC Settings Add-on? A 20 seconds timeout usually does it for Wifi.

eungenue · July 27, 2020 at 11:40 AM

Quote from Klojum

Any chance you have forgotten to enable the "Wait for network" option in the LibreELEC Settings Add-on? A 20 seconds timeout usually does it for Wifi.

Yes, I tried that option (up to 30 sec), but no success

t0phee · July 27, 2020 at 12:39 PM

Hi, I had an issue with time when I upgraded to a Pi4.

It turned out that there were not any ntp addresses in the correct gui location.

As I'm in the UK I added addresses two ntp server addresses to the confi: 0.uk.pool.ntp.org and 1.uk.pool.ntp.org. There is an option for a third, but I couldn't be bothered. The location is in the gui is >System>LibreELEC>Network and you will see NTP Servers.

HTH

eungenue · July 27, 2020 at 10:46 PM

Quote from t0phee

It turned out that there were not any ntp addresses in the correct gui location.

Thanks for the suggestion.

Yes, I've tried adding custom NTP servers to that list, but that didn't make the trick. BTW, I've read somewhere on the Internet, libreELEC has its own set of default NTP servers, so setting these in the GUI is optional.

What's interesting though is that I don't see it trying any of the custom servers at all. It just ignores this setting!

If that makes additional sense - the issue depends on the networks RPI is connected to. I've tried to use my cellphone Wifi tethering - and it worked normally. Unfortunately, not with my home connection. I've checked every possible setting on the router, but didn't see anything related or somehow linked to NTP. System time on the router is correct - so the NTP is accessible in provider network.

eungenue · July 28, 2020 at 8:41 PM

Seems like no suggestions?

Well, I haven't got to the bottom of this. Tried every possible log/option/idea that I could think of.

I believe the reason is somewhere inside systemd, when it decides that no time sync is needed:

Code

systemd[1]: Condition check resulted in Network Time Synchronization being skipped

Puzzled, I started writing simple NTP client myself, but then found a very nice way to query NTP servers right from the shell.

So I worked around the problem by adding this to .config/autorun.sh:

Code

sh -c 'while true; do date +%s -s@$((0x$(printf c%47s | nc -uw1 europe.pool.ntp.org 123 | /storage/xxd -s40 -l4 -p) - 2208988800)); sleep 3h; done' &

This starts sh in background that loops every 3h. It makes single UDP packet, sends it to europe.pool.ntp.org, parses the reply and sets system time from it. Funny, but this single line works _in place_ of all the systemd+ntpd+settings+headaches+whatever!

So far so good.

HTH

Oh, and this requires having xxd at hand, which LibreELEC doesn't have by default. So I've compiled it myself.

Unzip (forum doesn't allow tgz extensions) then copy to RPI and extract: tar -xvf xxd.tgz

xxd.tar.zip

jani · September 1, 2020 at 8:59 PM

I'm seeing the same problem on my Raspberry Pi 3b and Raspberry Pi 3b+. After a reboot, it sometimes successfully updates the time and sometimes it won't, so I'm thinking there's a race condition. "Wait for network = 60s" does not have any effect on this, nor setting the NTP servers.

systemctl status systemd-timesyncd prints this:

Code

Warning: The unit file, source configuration file or drop-ins of systemd-timesyncd.service changed on disk. Run 'systemctl daemon-reload'
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/systemd-timesyncd.service.d
└─depend-on-kernel-ip-config.conf
Active: inactive (dead)
Condition: start condition failed at Thu 2019-04-11 19:28:37 EEST; 1 years 4 months ago
└─ ConditionPathExists=/dev/.kernel_ipconfig was not met
Docs: man:systemd-timesyncd.service(8)


Apr 11 19:28:37 raspberry systemd[1]: Condition check resulted in Network Time Synchronization being skipped.

Display More

However, the same output is printed even if the time is set properly. Is systemd-timesyncd used for time sync?

EDIT: Also as a sidenote, systemctl daemon-reload won't make the warning disappear, I wonder why.

**mglae** · September 2, 2020 at 5:00 PM

Quote from jani

Is systemd-timesyncd used for time sync?

In normal configuration NTP is managed by connman. systemd-timesyncd is only used when the system is booted via PXE.

eungenue · October 23, 2020 at 9:01 AM

Wise people have pointed out that there is ntpdate utility that does NTP date sync. Can be installed on raspbian and taken to LibreELEC to be used instead of the monstrous cmd I posted earlier

Attached ntpdate that I've got on raspbian just in case

DanT · November 8, 2020 at 5:06 PM

It is mostly a guess, but I have observed this behaviour, when the electricity was switched-off in our street (due to maintenance :-))

Whet it has been restored again, the Raspberry (with libreELEC) was up earlier than the rest of the network. I mean, the devices in our house had addresses assigned by our local router, but the connection to the Internet has not been established yet (i.e. the NTP was inaccessible).

After manual reboot of the libreELEC Raspberry, the time has been set correctly. Other Raspberies, running Raspbian and systemd-networkd + systemd-timesyncd had the time set correctly.

Just my 2 cents ...

DanT · November 23, 2020 at 9:40 AM

I have opened an issue (4683) which has been closed shortly after with an explanation.

cpassuel · April 18, 2021 at 10:18 AM

I have the same issue with a Raspberry Pi Zero W. It seems to be related to wireless access.

I was struggling with this issue and found a python script to fix it Fix wrong date time on Raspberry Pi 3 in LibreELEC (Krypton) v8.0.1 MR (Kodi), when connected over WiFi · GitHub

Just follow the instruction in the comments and reboot. It's working fine

Connected but no date and nothing works

Similar Threads

Wifi sometimes works and sometimes not

No sound with LibreELEC + Kodi connected to One Connect Box (Samsung 75Q90R)

BT headphones connected, but no audio is heard