hi ricardo,
there is a bug setting the hardware clock when it is very far off from actual time. this has been fixed and will be released as part of the next update. in the meantime, you can get around this problem by:
- log in to the shake using an ssh connection
- set the date with the following command, picking a date and time relatively close to actual time (n.b., this must be UTC time, not local time):
> sudo date --set "2020-7-27 12:35:52" - and then reboot your unit
when the date and time is close to accurate, the ntpdate service executed at boot-up will succeed, your unit will connect to an NTP server, and will continually stay sync’ed to keep proper time.
hope this helps, let me know if you have any other questions,
richard