After the update to HAOS 15.0 the kernel time during start-up fails the task: “Wait Until Kernel Time Synchronized”. And then I see in the terminal:
[core-ssh ~]$ date
Tue Mar 25 22:24:54 -05 2025
Obviously, it wreaks havoc on everything, like “last backup was next week”.
I did reboot the VM, and the host PC, and the WiFi multiple times. The network connection seems fine: ifconfig shows no errors, the ping to all the timeservers on Internet fine, etc.
What else should I check, or how can I set the correct time on my system?
Open the console on the HA server, then type login and when you are logged in then use the date command to set the date and time.
Hi Vadim, welcome to the forum!
There are some issues with the update to HAOS v15.0 GitHub · Where software is built
“date -s” is not permitted:
[core-ssh ~]$ date -s “2025-03-18 22:47”
date: can’t set date: Operation not permitted
Tue Mar 18 22:47:00 -05 2025
[core-ssh ~]$ date
Wed Mar 26 04:58:30 -05 2025
[core-ssh ~]$ whoami
root
I installed the Chrony add-on. Getting the correct time now. But this is a kludge, isn’t it?
I run Chrony myself, because it makes small adjustments to the time all the time, so you do not get large drifts in time when running in a VM.
the SNTP that normally sets the time is only run a few times during the day and the time can actually drift quite a bit on VM setups. It is especially far off just before a SNTP execution.