Hello community, I do have issues with the timesychronization of VMs in my Qubes OS 4.1.1 system.
I was reading the information provided in [1] - and - verified that 'sys-net' is my clock VM. However I was not able to resolve my issues ... Here are the logs: <Log-1> [vr@dom0 ~]$ qubes-prefs clockvm sys-net [vr@dom0 ~]$ </Log-1> <Log-2> [user@sys-net ~]$ [user@sys-net ~]$ timedatectl Local time: Sat 2022-07-23 19:54:36 CEST Universal time: Sat 2022-07-23 17:54:36 UTC RTC time: Sat 2022-07-23 17:54:36 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: no NTP service: inactive RTC in local TZ: no [user@sys-net ~]$ </Log-2> <Log-3> [user@sys-net ~]$ [user@sys-net ~]$ systemctl restart systemd-timesyncd [user@sys-net ~]$ [user@sys-net ~]$ [user@sys-net ~]$ systemctl status systemd-timesyncd ○ systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled> Drop-In: /usr/lib/systemd/system/systemd-timesyncd.service.d └─30_qubes.conf Active: inactive (dead) Condition: start condition failed at Sat 2022-07-23 20:06:48 CEST; 14s ago └─ ConditionPathExists=/var/run/qubes-service/clocksync was not met Docs: man:systemd-timesyncd.service(8) lines 1-8/8 (END) [user@sys-net ~]$ </Log-3> <Log-4> [user@sys-net ~]$ [user@sys-net ~]$ cd /var/run/qubes-service [user@sys-net qubes-service]$ ls network-manager qubes-network qubes-updates-proxy qubes-firewall qubes-update-check [user@sys-net qubes-service]$ </Log-4> Do you have any advice on how to continue from here - or - what else to check? With kind regards, Viktor --- [1] https://github.com/Qubes-Community/Contents/blob/master/docs/system/clock-time.md -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9d6644d7-4e4e-491e-a4d2-4a372304bc69n%40googlegroups.com.