Hello, why is Raspberry Pi OS too dependent on date/time synchronization (NTP time)?
On my home network is forbidden NTP protocol by ISP provider (I don't know why, tried to solve it with them but without success![:roll:]( "Rolling Eyes")
)
Yes I know, date/time can be set manually, and there is some accuracy tolerance. For sudo update/upgrade it is around minute or so.
But if you want use quite new (beta) Raspberry Pi Connect service, then simple remote restart (mostly after remote update/upgrade) cause that Pi will not be accessible over Internet, and the time difference is very small after restart.
I tried to solve it and finally did python script, which takes time from website "just-the-time.appspot.com", convert it to correct timezone and by "sudo date" force it to the system, and repeat it by cron every 10 minutes. So there can be problem with connection maximum 10 minutes after restart. Tested it and working even after restart which can cause big time difference when there is no NTP synchronization.
But I use other Raspberry Pi 4B without monitor, keyboard, mouse or anything, on different place and different network where NTP time service is normally working, but when I remotely restarted it after update/upgrade, then it stays inaccessible over Internet via Raspberry Pi Connect. It only shows information "last seen less than a minute ago" or "1 minute ago". But impossible to connect. So there is problem to connect it even if time is synchronized by NTP.
It is running on Raspberry Pi OS 64bit Bookworm with desktop (July 4th 2024 release), system is clean, stock, all settings in default except moving taskbar to bottom, did update/upgrade, connect to local wifi and installed 1 application.
When I went there with monitor and keyboard to find out the problem, then it was connected normally, everything is working, time difference must be maybe 1 second. When I set time manually via sudo date, then raspberry was normally accessible via Raspberry Pi connect after maybe 30 seconds.
It is possible to do system (or at least Pi connect) not too dependent on date/time synchronization to correct work when it is synchonized by NTP? Because then the headless Pi is useless and it is working only when I force date/time "manually" via the same python script. I think it is little crazy to override system "acurate NTP time" by time taken from some website by script in order to be able to use remote access.
On my home network is forbidden NTP protocol by ISP provider (I don't know why, tried to solve it with them but without success
)Yes I know, date/time can be set manually, and there is some accuracy tolerance. For sudo update/upgrade it is around minute or so.
But if you want use quite new (beta) Raspberry Pi Connect service, then simple remote restart (mostly after remote update/upgrade) cause that Pi will not be accessible over Internet, and the time difference is very small after restart.
I tried to solve it and finally did python script, which takes time from website "just-the-time.appspot.com", convert it to correct timezone and by "sudo date" force it to the system, and repeat it by cron every 10 minutes. So there can be problem with connection maximum 10 minutes after restart. Tested it and working even after restart which can cause big time difference when there is no NTP synchronization.
But I use other Raspberry Pi 4B without monitor, keyboard, mouse or anything, on different place and different network where NTP time service is normally working, but when I remotely restarted it after update/upgrade, then it stays inaccessible over Internet via Raspberry Pi Connect. It only shows information "last seen less than a minute ago" or "1 minute ago". But impossible to connect. So there is problem to connect it even if time is synchronized by NTP.
It is running on Raspberry Pi OS 64bit Bookworm with desktop (July 4th 2024 release), system is clean, stock, all settings in default except moving taskbar to bottom, did update/upgrade, connect to local wifi and installed 1 application.
When I went there with monitor and keyboard to find out the problem, then it was connected normally, everything is working, time difference must be maybe 1 second. When I set time manually via sudo date, then raspberry was normally accessible via Raspberry Pi connect after maybe 30 seconds.
It is possible to do system (or at least Pi connect) not too dependent on date/time synchronization to correct work when it is synchonized by NTP? Because then the headless Pi is useless and it is working only when I force date/time "manually" via the same python script. I think it is little crazy to override system "acurate NTP time" by time taken from some website by script in order to be able to use remote access.
Statistics: Posted by lukuc — Sat Jul 13, 2024 7:39 pm