[ViX_Misc] Why are all my log files dated 01-01-1970?

[amspa]

Hi,

All of my debug log files are dated 01-01-1970. They all follow this pattern:

Enigma2-01-01-1970_01-00-XX.log

Why is it doing this? Can anyone help me get these log files dated properly as at the moment it's very difficult to know which log file relates to which crash!

The time on the box itself is correct. I've set the time using both NTP and transponder and the problem remains either way.

Also, on an unrelated point, why are the entries in the log files themselves not time-stamped? Trying to find the cause of a problem in a massive debug log would be much easier if you could tell when each event occurred.

One final debug log related thing. Sometimes when the box freezes I need to turn it off at the switch and restart it to get it back working. Most of the time when I do this (not always) the debug log disappears leaving me with no way to find out what's causing the freezing. Is there a way to prevent this happening?

I'm running Vix Apollo, build 70 on a Gigablue Quad+

Thanks

 

[judge]

Restart E2 for debug logs to get correct time in file names.

 

[Joe_90]

The debug logs are getting a default timestamp of 1/1/70 @ 01:00 plus some seconds because the realtime clock does not seem to work on any of these boxes (or linux/enigma does not know how to retrieve the realtime clock from the front panel controller) when they are booted from deep standby and the linux clock starts from this date. The clock information is subsequently pulled from the network connection (NTP) or from the transponder you are tuned to and seems to be ok once you are in normal operation or in normal standby. Coupled with that there is a default setting in the log handling which deletes logs which are more than 30 days old and 1/1/70 is ALWAYS more than 30 days old. I've reported the deletion problem as a bug, but there are other pressing bugs and enhancements taking priority.

I'm not sure why the actual clock time can't be pulled from the front panel controllers as the little googling I've done would seem to indicate that most hardware actually supports a real time clock in deep standby. It has to support some kind of clock function in any case as it needs to wake the box up at intervals.