[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.
[qubes-users] Re: Problem upgrading to 4.1.1. - computer freezes
You are in the current version of Qubes. You don't need to upgrade to another fedora version as it is in 32. This might be Intel ME thing to crash your PC. A full complete reinstallation is NOT required for your PC as you need to try many times in order to work. The logs that output is well-normal at this point on because of older components needs time to recognize and train overtime. However, it will cause your PC to slow down. Are you sure that the Intel ME in your PC turned on? On Saturday, July 30, 2022 at 11:47:58 AM UTC-7 Votan wrote: > Dear all, > > I was running on Qubes OS 4.1 with kernel 5.10.112 > > After updating with the Qubes Update Tool, my computer did not reboot > anymore - it froze at the point when the password for the system needs to > be entered. I still have the previous version, so I can still boot into the > system with version 4.1. > > As a second step I tried to update via command line in dom0 as suggested > here (qubes-os.org/doc/upgrade/4.1): > > > sudo qubes-dom0-update -y qubes-dist-upgrade > > Yet I get as error message: No match found for argument: qubes-dist-upgrade > > > Any idea how to debug this? When I boot into the old version, I will not > learn from the logs. I am stuck. > > > Do I need a complete re-install? > > Hardware: > > Dell XPS 15 > > Intel Core i7-11800H > > 64GB RAM > > > Yours > > Votan > -- 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/6ef6c758-51e5-420b-bd09-d7841d1341abn%40googlegroups.com.
[qubes-users] Problem upgrading to 4.1.1. - computer freezes
Dear all, I was running on Qubes OS 4.1 with kernel 5.10.112 After updating with the Qubes Update Tool, my computer did not reboot anymore - it froze at the point when the password for the system needs to be entered. I still have the previous version, so I can still boot into the system with version 4.1. As a second step I tried to update via command line in dom0 as suggested here (qubes-os.org/doc/upgrade/4.1): > sudo qubes-dom0-update -y qubes-dist-upgrade Yet I get as error message: No match found for argument: qubes-dist-upgrade Any idea how to debug this? When I boot into the old version, I will not learn from the logs. I am stuck. Do I need a complete re-install? Hardware: Dell XPS 15 Intel Core i7-11800H 64GB RAM Yours Votan -- 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/57aa6aba-cdf7-5e8a-5d7b-c914eeef4253%40posteo.de.
