Hey, I’m running into a pretty unfortunate problem with HassOS as of about a day or so ago involving the current system time of home assistant showing up as “2118-01-25”.
When checking the “host logs”, I see this message:
Jan 25 08:18:01 homeassistant systemd[1]: Started Hostname Service.
Jan 25 08:18:01 homeassistant systemd[1]: Starting Time & Date Service...
Jan 25 08:18:01 homeassistant kernel: audit: type=1334 audit(4672541881.689:4601): prog-id=2167 op=LOAD
Jan 25 08:18:01 homeassistant kernel: audit: type=1334 audit(4672541881.689:4602): prog-id=2168 op=LOAD
Jan 25 08:18:01 homeassistant kernel: audit: type=1334 audit(4672541881.689:4603): prog-id=2169 op=LOAD
Jan 25 08:18:01 homeassistant systemd[1]: Started Time & Date Service.
Jan 25 08:18:09 homeassistant systemd-timesyncd[443]: Failed to call clock_adjtime(): Invalid argument
Jan 25 08:18:31 homeassistant systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Jan 25 08:18:31 homeassistant kernel: audit: type=1334 audit(4672541911.807:4604): prog-id=0 op=UNLOAD
Jan 25 08:18:31 homeassistant kernel: audit: type=1334 audit(4672541911.807:4605): prog-id=0 op=UNLOAD
Jan 25 08:18:31 homeassistant kernel: audit: type=1334 audit(4672541911.807:4606): prog-id=0 op=UNLOAD
Jan 25 08:18:31 homeassistant systemd[1]: systemd-timedated.service: Deactivated successfully.
Jan 25 08:18:32 homeassistant kernel: audit: type=1334 audit(4672541911.999:4607): prog-id=0 op=UNLOAD
Jan 25 08:18:32 homeassistant kernel: audit: type=1334 audit(4672541911.999:4608): prog-id=0 op=UNLOAD
Jan 25 08:18:32 homeassistant kernel: audit: type=1334 audit(4672541911.999:4609): prog-id=0 op=UNLOAD
Jan 25 08:18:41 homeassistant systemd-timesyncd[443]: Failed to call clock_adjtime(): Invalid argument
There doesn’t seem to be any more details on what the invalid arguments were when calling the function which makes this a bit hard to debug further.
Any pointers would be much appreciated!
PS: The timezone settings are correct though I didn’t expect that to be the issue anyway since the problem seems to stem from the host machine and not the hassOS install itself.
The problems caused by this is everything that needs to check a certificate seems to think my cert has expired (expires sometime in 2023). This includes all of my cloud-based integrations, addon installation, creating and restoring backups. TL;DR: it’s a pretty crippling issue.
I had rebooted the instance through home assistant a few times but it took me a while to realize I should just try resetting the odroid 