Web ui shows wrong date and time after bios reset

Insight & Feedback ZimaOS Open Beta
22

At present, TimeDateCTL is only responsible for obtaining the time zone, and the subsequent time calculation is handled internally by Go

23
  1. Is the time displayed normal or is there still a problem?
  2. Before you set the BIOS time, is the BIOS time in 2024 as of the video you posted above?
  3. Is there still a problem with the shutdown function?
24

The last I tried the shut is working.
I also tried changing the Time Zone to get the correct time display, doesn’t make any difference.
In the end I turned the widget off

25

the time is now coming from bios settings (i set it now manually)
now the difference is just about a minute, i still see the brief change of time as i login in the webui but i think it’s not a big deal
shutdown is now working fine!

1 Like
26

OK, but this doesn’t actually answer my question…

Is there an automatic time sync or not?

27

i don’t know
how can i check?

28

Is this helpful? @WuzzyFeasel @alegggiu

29

Honestly, not yet.

I was curious if ZimaOS does sync the hardware clock automatically and if yes, how often. For a server, a correct system time is crucial for stuff like OTP.

@LinkLeong announced it for version 1.2.5.

I checked myself with timedatectl status:

               Local time: Tue 2025-06-03 13:35:56 CEST
           Universal time: Tue 2025-06-03 11:35:56 UTC
                 RTC time: Tue 2025-06-03 11:35:56
                Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no

and systemctl status systemd-timesyncd:

○ systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: enabled)
     Active: inactive (dead)
       Docs: man:systemd-timesyncd.service(8)

So it doesn’t look like. Unless it is hidden in some startup or shutdown script.

30

is it ok like this?

root@ZimaOS:~# timedatectl
Local time: Tue 2025-06-03 15:42:58 CEST
Universal time: Tue 2025-06-03 13:42:58 UTC
RTC time: Tue 2025-06-03 13:42:58
Time zone: Europe/Rome (CEST, +0200)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no
root@ZimaOS:~# timedatectl set-ntp true
root@ZimaOS:~# timedatectl
Local time: Tue 2025-06-03 15:43:50 CEST
Universal time: Tue 2025-06-03 13:43:50 UTC
RTC time: Tue 2025-06-03 13:43:50
Time zone: Europe/Rome (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

31

image
image567×189 4.18 KB

This has been fixed and needs to be verified in 1.4.2

Or can you help us verify in advance? I can send you 1.4.2-alpha1.raucb

32

Sure!

1 Like
34

wget https://casaos.oss-cn-shanghai.aliyuncs.com/IceWhaleTech/zimaos-rauc/extenal-package/zimaos_zimacube-1.4.2-alpha1.raucb and rauc install

1 Like
35

Yes, this works fine now!

timedatectl status:

               Local time: Mon 2025-06-16 11:46:45 CEST
           Universal time: Mon 2025-06-16 09:46:45 UTC
                 RTC time: Mon 2025-06-16 09:46:45
                Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

systemctl status systemd-timesyncd:

○ systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: enabled)
     Active: active (running) since Mon 2025-06-16 11:34:15 CEST; 12min ago
 Invocation: 13ac9e4cdc3346a98370bdad39088d11
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 589 (systemd-timesyn)
     Status: "Contacted time server 128.138.140.44:123 (time.nist.gov)."
      Tasks: 2 (limit: 38103)
     Memory: 1.5M (peak: 2.7M)
        CPU: 57ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─589 /usr/lib/systemd/systemd-timesyncd

Jun 16 11:34:15 ZimaOS systemd[1]: Starting Network Time Synchronization...
Jun 16 11:34:15 ZimaOS systemd[1]: Started Network Time Synchronization.
Jun 16 11:34:22 ZimaOS systemd-timesyncd[589]: Network configuration changed, trying to establish connec
Jun 16 11:34:22 ZimaOS systemd-timesyncd[589]: Network configuration changed, trying to establish connec
Jun 16 11:34:23 ZimaOS systemd-timesyncd[589]: Network configuration changed, trying to establish connec
Jun 16 11:34:25 ZimaOS systemd-timesyncd[589]: Network configuration changed, trying to establish connec
Jun 16 11:34:27 ZimaOS systemd-timesyncd[589]: Contacted time server 128.138.140.44:123 (time.nist.gov).
Jun 16 11:34:27 ZimaOS systemd-timesyncd[589]: Initial clock synchronization to Mon 2025-06-16 11:34:27.
2 Likes