[OS-mio+] Time

[EnoSat]

Without a TDT/TOT signal, the time is reset to zero even though NTP update is enabled

<  1718.6146> [eConsoleAppContainer] Starting /usr/bin/grab
<  1719.2098> [eConsoleAppContainer] user kill(SIGKILL)
<  1842.6918> [NetworkTime] Updating from NTP
<  1842.6920> [Console] command: ['/usr/sbin/ntpd', '/usr/sbin/ntpd', '-nq', '-p', 'sk.pool.ntp.org']
<  1842.6921> [eConsoleAppContainer] Starting /usr/sbin/ntpd
<  1843.8221> [Console] finished: /usr/sbin/ntpd
<  1843.8222> [NetworkTime] setting E2 time: 1703622660.4975019
<  1843.8260> [StbHardware] Set RTC to Ut 26 dec 2023  21:31 (rtc_offset = 3600 sec.)
<  1843.8267> [StbHardware] Error: setRTCtime failed!
<  1843.8268> [eDVBLocalTimerHandler] setUseDVBTime: current=ntp, new=ntp
<  1843.8282> Timing out client: IPv6Address(type='TCP', host='::ffff:192.168.1.50', port=59426, flowInfo=0, scopeID=0)
<  1843.8288> Timing out client: IPv6Address(type='TCP', host='::ffff:192.168.1.50', port=59462, flowInfo=0, scopeID=0)
<  1882.3488> [eDVBLocalTimerHandler] no transponder tuned... or no TDT/TOT avail .. try to use RTC :)
<  1882.3491> [eDVBLocalTimerHandler] RTC time is 01:31:29
<  1882.3491> [eDVBLocalTimerHandler] Receiver time is 21:31:39
<  1882.3491> [eDVBLocalTimerHandler] RTC to Receiver time difference is 1703620810 seconds
<  1882.3491> [eDVBLocalTimerHandler] set Linux Time to RTC Time
<  1924.3306> [timer.py] timewarp - re-evaluating all processed timers.
<  1924.3307> [timer.py] timewarp - re-evaluating all processed timers.
<  2020.0544> [AutoTimer] current auto poll 1970-01-01 01:33:46
<  2020.0546> [AutoTimer] Auto Poll Started
<  2020.0548> [AutoTimer] No changes in configuration, won't parse
<  2020.0561> [Task] job Components.Task.Job name=AutoTimer #tasks=0 completed with [] in None
<  2020.0565> [AutoTimer] next auto poll at 1970-01-01 02:03:46

 

[Orlandox]

Is that NTP address correct ? 'sk.pool.ntp.org', try with 'pool.ntp.org' instead.

 

[birdman]

Is that NTP address correct ? 'sk.pool.ntp.org', try with 'pool.ntp.org' instead.

Looks OK to me:

[FONT=monospace][COLOR=#000000][gmllaptop]: host sk.pool.ntp.org [/COLOR]
sk.pool.ntp.org has address 213.160.182.226 
sk.pool.ntp.org has address 212.55.254.189 
sk.pool.ntp.org has address 213.81.129.99 
sk.pool.ntp.org has address 185.242.56.5
[/FONT]

 

[Valiant]

Without a TDT/TOT signal, the time is reset to zero even though NTP update is enabled

<  1718.6146> [eConsoleAppContainer] Starting /usr/bin/grab
<  1719.2098> [eConsoleAppContainer] user kill(SIGKILL)
<  1842.6918> [NetworkTime] Updating from NTP
<  1842.6920> [Console] command: ['/usr/sbin/ntpd', '/usr/sbin/ntpd', '-nq', '-p', 'sk.pool.ntp.org']
<  1842.6921> [eConsoleAppContainer] Starting /usr/sbin/ntpd
<  1843.8221> [Console] finished: /usr/sbin/ntpd
<  1843.8222> [NetworkTime] setting E2 time: 1703622660.4975019
<  1843.8260> [StbHardware] Set RTC to Ut 26 dec 2023  21:31 (rtc_offset = 3600 sec.)
<  1843.8267> [StbHardware] Error: setRTCtime failed!
<  1843.8268> [eDVBLocalTimerHandler] setUseDVBTime: current=ntp, new=ntp
<  1843.8282> Timing out client: IPv6Address(type='TCP', host='::ffff:192.168.1.50', port=59426, flowInfo=0, scopeID=0)
<  1843.8288> Timing out client: IPv6Address(type='TCP', host='::ffff:192.168.1.50', port=59462, flowInfo=0, scopeID=0)
<  1882.3488> [eDVBLocalTimerHandler] no transponder tuned... or no TDT/TOT avail .. try to use RTC :)
<  1882.3491> [eDVBLocalTimerHandler] RTC time is 01:31:29
<  1882.3491> [eDVBLocalTimerHandler] Receiver time is 21:31:39
<  1882.3491> [eDVBLocalTimerHandler] RTC to Receiver time difference is 1703620810 seconds
<  1882.3491> [eDVBLocalTimerHandler] set Linux Time to RTC Time
<  1924.3306> [timer.py] timewarp - re-evaluating all processed timers.
<  1924.3307> [timer.py] timewarp - re-evaluating all processed timers.
<  2020.0544> [AutoTimer] current auto poll 1970-01-01 01:33:46
<  2020.0546> [AutoTimer] Auto Poll Started
<  2020.0548> [AutoTimer] No changes in configuration, won't parse
<  2020.0561> [Task] job Components.Task.Job name=AutoTimer #tasks=0 completed with [] in None
<  2020.0565> [AutoTimer] next auto poll at 1970-01-01 02:03:46

< 1882.3491> [eDVBLocalTimerHandler] RTC time is 01:31:29
< 1882.3491> [eDVBLocalTimerHandler] Receiver time is 21:31:39
< 1882.3491> [eDVBLocalTimerHandler] RTC to Receiver time difference is 1703620810 seconds

Is the difference between these two times really 1.7 Billion seconds?

 

[adm]

< 1882.3491> [eDVBLocalTimerHandler] RTC time is 01:31:29
< 1882.3491> [eDVBLocalTimerHandler] Receiver time is 21:31:39
< 1882.3491> [eDVBLocalTimerHandler] RTC to Receiver time difference is 1703620810 seconds

Is the difference between these two times really 1.7 Billion seconds?

The OP image shows a date of 1st Jan 1970. (Approx) 1.7 billion seconds is the difference between now and 1970. I there is a real time clock (RTC) in the box then 1970 would be the date/time it may indicate if it wasn't powered by a battery backup.

Random Google search
The date January 1, 1970, is significant in computing because it is the starting point of the Unix time system, which is a way to track time in computing. In Unix and many other systems, time is often stored as the number of seconds that have elapsed since midnight on January 1, 1970. When a computer encounters an error in calculating dates, it may revert to this default time as a way to handle the error and prevent crashes or unpredictable behavior. This default time is also known as the "epoch time".

 

[Valiant]

Yes I know about the unix start time, but the two lines clearly state two times and the third states the difference between them which is obviously nonsense.

 

[birdman]

Yes I know about the unix start time, but the two lines clearly state two times and the third states the difference between them which is obviously nonsense.

It's not nonsense if you consider the date (and timezone), not just the time.