Posts by Tos26

Ok, thanks.

The only difference is that camera is out the dhcp domain.

Yes

Ok but as I said, my IP camera gets the time from NTP through the same wifi modem/router.

I will try the workaround you proposed but I'm a little bit frustrated to not understand the root cause.

Many thanks for your help and if you have a new idea, don't hesitate to post it

And if I find the solution, I will post it here.

Ok done.

I added the -v option to have more detail: http://ix.io/1bqh

It seems correct : http://ix.io/jit

What is the best addon for the test : System tools or network tools ? And what kind of test can I perform with these tools ?

Last results:

No firewall on my side and I hope the new firewall integrated in Libreelec is really disable when Disable is displayed on the interface.

I have also on my local network an IP camera wifi connected on the same modem/router and the NTP runs normally, so to me, there is no problem with the firewall in the router.

Command curl is ok.

here is the last test of ntp server: Time out but ping ok.

LibreELEC:~ # ntpd -d -d -d -n -p pool.ntp.org
ntpd: 'pool.ntp.org' is 212.83.145.32
ntpd: sending query to 212.83.145.32
ntpd: poll:16s sockets:1 interval:1s
ntpd: timed out waiting for 212.83.145.32, reach 0x00, next query in 1s
ntpd: 'pool.ntp.org' is 212.83.145.32
ntpd: poll:2s sockets:0 interval:1s
ntpd: sending query to 212.83.145.32
ntpd: poll:16s sockets:1 interval:1s
^C
LibreELEC:~ # ping 212.83.145.32
PING 212.83.145.32 (212.83.145.32): 56 data bytes
64 bytes from 212.83.145.32: seq=0 ttl=56 time=43.036 ms
64 bytes from 212.83.145.32: seq=1 ttl=56 time=43.323 ms
64 bytes from 212.83.145.32: seq=2 ttl=56 time=41.918 ms
64 bytes from 212.83.145.32: seq=3 ttl=56 time=44.194 ms
64 bytes from 212.83.145.32: seq=4 ttl=56 time=42.694 ms
^C
--- 212.83.145.32 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 41.918/43.033/44.194 ms
LibreELEC:~ # 

Am I alone with this strange behavior ?

Result of the first command line:

LibreELEC:~ # ntpd -d -d -d -n -p pool.ntp.org
ntpd: 'pool.ntp.org' is 163.172.10.212
ntpd: sending query to 163.172.10.212
ntpd: poll:16s sockets:1 interval:1s
ntpd: timed out waiting for 163.172.10.212, reach 0x00, next query in 1s
ntpd: 'pool.ntp.org' is 163.172.10.212
ntpd: poll:2s sockets:0 interval:1s
ntpd: sending query to 163.172.10.212
ntpd: poll:16s sockets:1 interval:1s
ntpd: timed out waiting for 163.172.10.212, reach 0x00, next query in 1s
ntpd: 'pool.ntp.org' is 163.172.10.212
ntpd: poll:2s sockets:0 interval:1s
ntpd: sending query to 163.172.10.212
ntpd: poll:16s sockets:1 interval:1s
ntpd: timed out waiting for 163.172.10.212, reach 0x00, next query in 1s
ntpd: 'pool.ntp.org' is 163.172.10.212
ntpd: poll:2s sockets:0 interval:1s
ntpd: sending query to 163.172.10.212
ntpd: poll:16s sockets:1 interval:1s

And the second one:

http://ix.io/1bjj

vpeter :

I added autostart.sh with your code, sleep 5 nok, then sleep 20 nok.

Here is the log file

I don't think that's a timing problem, because the time is syncing when I plug the ethernet cable even after one hour but never synced with the wifi, despite the retries.

No I don't. I have another Raspberry 3. I don't know if this kind of test is relevant. I can try.

Hello.

I use the on board PI wifi.

Hello,

I restarted my Kodi with NTP server address configured as 95.81.173.74 ==> No time and date sync !! Log file (Lines before the tag Reboot, time 13:11 / 13:12)

Ping on 95.81.173.74 is correct. However, in the logfile, we find:

Jun 22 13:12:03 LibreELEC connmand[287]: ../src/timeserver.c:ntp_callback() success 0
Jun 22 13:12:03 LibreELEC connmand[287]: ../src/timeserver.c:sync_next() Using timeserver 95.81.173.74
Jun 22 13:12:03 LibreELEC connmand[287]: ../src/ntp.c:start_ntp() server 95.81.173.74 family 2
Jun 22 13:12:05 LibreELEC connmand[287]: ../src/ntp.c:send_timeout() send timeout 0 (retries 0)
Jun 22 13:12:05 LibreELEC connmand[287]: ../src/ntp.c:send_timeout() send timeout 0 (retries 1)
Jun 22 13:12:05 LibreELEC connmand[287]: ../src/ntp.c:send_timeout() send timeout 0 (retries 2)
Jun 22 13:12:05 LibreELEC connmand[287]: ../src/ntp.c:send_timeout() send timeout 0 (retries 3)
Jun 22 13:12:05 LibreELEC connmand[287]: ../src/timeserver.c:ntp_callback() success 0
Jun 22 13:12:05 LibreELEC connmand[287]: ../src/timeserver.c:sync_next() Resolving timeserver 2.pool.ntp.org

Here is a summary of my situation:

1. Kodi 8.2.5:
   • Modem/Router from ISP.
   • Raspberry PI3 B+
   • Ethernet link => NTP OK
   • Wifi => NTP OK
2. Kodi 9.0.0:
   • Same Modem/Router from ISP.
   • Same Raspberry PI3 B+
   • Ethernet link => NTP OK
   • Wifi => NTP NOK
     
   • Wifi access point on 4G smartphone => NTP OK.
     

It's a big mystery for me, I understand nothing anymore.

Thank you Chewitt for your answer.

I added debugging to boot params in cmdline.txt.

Here is the log file

I'm not sure it's enough, I don't know where are the systemd journal and the log of connman in the system.

Could you tell me if information in the provided log file is relevant ?

Hello again,

I found the exact same issue than me in this post.

So, despite the manual change of IP address to IPV4 in the LE settings, the issue remains the same: Libreelec tries to access to NTP server thru IPV6 address. See Log file.

I begin to believe this is a LE bug, not yet fixed. Maybe Chewitt can give his advice...

Hello,

I decided to install LE 9.0.0 from scratch instead of upgrade from 8.2.5.

And unfortunately, I got the same issue: Wifi connected but NTP error and bad Time and date.

Is there someone with the same issue ?

I need help please...

Hello,

I upgraded my LE from 8.2.5 to 9.0.0. No problem at the reboot.

I'm connected trough Wifi. The status of the connection is good (DHCP, IP given, online, etc...) but I have bad date and time. So, all SSL connections fail.

It seems that the first connection to NTP server fails and I don't know why. With LAN, there is no problem.

And before the upgrade, with version 8.2.5, there was no problem.

Log file

I'm on raspberry PI3 B+.

Someone could help me?