Re: [qubes-users] Re: Problems with Timesynchronization
> > Can you please comment on how it is possible, that > "ConditionPathExists=/var/run/qubes-service/clocksync was not met" - and - > ideally, how to resolve that issue. > That suggests that you do not have the clocksync service enabled. Set it with `qvm-service --enable QUBE clocksync` or `qvm-features QUBE service.clocksync 1` -- 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/YuZmeyeQ/YQ9JZb4%40thirdeyesecurity.org.
[qubes-users] Re: Problems with Timesynchronization
Did you check any system errors during the update? On Saturday, July 30, 2022 at 9:34:26 PM UTC-7 viktor@gmail.com wrote: > Hello Community, > > No advice / feedback at all ? > > Viktor Ransmayr schrieb am Samstag, 23. Juli 2022 um 22:05:39 UTC+2: > >> 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: >> >> >> >> [vr@dom0 ~]$ qubes-prefs clockvm >> sys-net >> [vr@dom0 ~]$ >> >> >> >> >> >> [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 ~]$ >> >> >> >> >> >> [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 ~]$ >> >> >> >> >> >> [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]$ >> >> >> >> Do you have any advice on how to continue from here - or - what else to >> check? >> > > Can you please comment on how it is possible, that > "ConditionPathExists=/var/run/qubes-service/clocksync was not met" - and - > ideally, how to resolve that issue. > > With kind regards, > > Viktor > > -- 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/99367f6d-9f30-4602-b650-55a72d5d8aacn%40googlegroups.com.
[qubes-users] Re: Problems with Timesynchronization
Hello Community, No advice / feedback at all ? Viktor Ransmayr schrieb am Samstag, 23. Juli 2022 um 22:05:39 UTC+2: > 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: > > > > [vr@dom0 ~]$ qubes-prefs clockvm > sys-net > [vr@dom0 ~]$ > > > > > > [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 ~]$ > > > > > > [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 ~]$ > > > > > > [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]$ > > > > Do you have any advice on how to continue from here - or - what else to > check? > Can you please comment on how it is possible, that "ConditionPathExists=/var/run/qubes-service/clocksync was not met" - and - ideally, how to resolve that issue. With kind regards, Viktor -- 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/28050d33-a4c4-4daf-8372-da94989f7644n%40googlegroups.com.
