On Friday, October 5, 2018 at 3:26:51 PM UTC-4, Ivan Mitev wrote: > Every time I had a "failed to synchronize..." erorr it was because there > was a problem with the proxy in sys-net. Restarting it usually did the > trick, eg: > > sudo systemctl restart qubes-updates-proxy.service > > (run the command sys-net ; the syntax is for R4.0, I don't have R3.2 to > test but it shouldn't be too different). > > Check the proxy's status with > > sudo systemctl status qubes-updates-proxy.service
Thanks for your help and suggestion. I just tried both of those commands and sys-net reports the update proxy is working perfectly, however there is no change in the result from dom0 and I get the same error message as before. The original interruption glitch happened after dom0 had already successfully downloaded all updates, but during the upgrade/install of those new packages. Ever since then, this issue has occurred. So I am thinking something local has gotten messed up rather than a connection issue. Any other ideas I should try in order to fix this? Thanks... -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ce59a818-cea9-4f59-a782-9557d8b48273%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
