Re: [qubes-users] Fedora25 fails updates unless I reboot the machine 9.13.17
On Thursday, October 5, 2017 at 9:38:50 AM UTC-4, Bill Wether wrote: > On my thinkpad 430, I fix this by setting sys-firewall's netvm to 'none', > restarting sys-net, and setting it back. Works every time so far. > > Cheers > > BillW what about just removing the sys-net and recreating it. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c52294c0-af5a-467d-84f5-66c45a08c291%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fedora25 fails updates unless I reboot the machine 9.13.17
On my thinkpad 430, I fix this by setting sys-firewall's netvm to 'none', restarting sys-net, and setting it back. Works every time so far. Cheers BillW -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0de43eab-9419-4cd1-b053-b305b5245815%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fedora25 fails updates unless I reboot the machine 9.13.17
I'm experiencing a similar problem which I've reported a bug for at https://github.com/QubesOS/qubes-issues/issues/3135 If you're still encountering the issue with the update proxy failing too, could you check the output of "journalctl -u qubes-updates-proxy.service" when it fails please? Marek also asked whether I have a broken network cable (n/a) or poor wifi (signal seems strong enough, i.e. no dropouts and problem occurs across different wifi networks), so it would be good to know that for you too. If you don't like github, happy to post any responses here into the ticket I have open. I've found a workaround (specified in the ticket) that fixes it for me, but interested to know if we're dealing with one problem, or different ones. 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bumk34huiaO0hR8GdTU-HteBpeYDys3Z61RGy68KKgXkOb3lYT7BHoGQaxUxBVJERY52j6tsT42DVZEJAMo4nILhFK8HF5o7iegYzezsFo4%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fedora25 fails updates unless I reboot the machine 9.13.17
On 2017-09-14 03:51, Robert Fisk wrote: > On 09/14/2017 10:49 AM, qubester wrote: >> Fedora25 fails updates unless I reboot the machine 9.13.17 >> >> 2 or 3 times now, are others having this problem? is there some >> particular remedy or just let it go? >> >> "failed to syncronize cache" >> > > I see this problem on a Q3.2 system that has been running for several days. > > Updating Fedora 25 template: >> sudo dnf update >> Error: Failed to synchronize cache for repo 'updates' > > Updating Debian 9 template: >> sudo apt update >> Err:1 http://security.debian.org stretch/updates >> InRelease >> Could not connect to 10.137.255.254:8082 (10.137.255.254), connection >> timed out >> Err:2 http://deb.qubes-os.org/r3.2/vm stretch >> InRelease >> Could not connect to 10.137.255.254:8082 (10.137.255.254), connection >> timed out >> Err:3 http://deb.debian.org/debian stretch >> InRelease >> Could not connect to 10.137.255.254:8082 (10.137.255.254), connection >> timed out >> Err:4 http://deb.debian.org/debian stretch-updates InRelease >> Unable to connect to 10.137.255.254:8082: > > Dom0 update seems to work (or at least fails silently): >> sudo qubes-dom0-update >> Using sys-firewall as UpdateVM to download updates for Dom0; this may >> take some time... >> Running command on VM: 'sys-firewall'... >> Running command on VM: 'sys-firewall'... >> Checking for dom0 updates... >> No new updates available > > > Restarting fixes the problem temporarily. I guess the update proxy is > crashing? My sys-firewall is running a Debian 9 template, what about yours? > > Regards, > Robert Are you saying by chance, that if I changed the template that the sys-firewall is based on, that that might fix this ? -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/30520dcf9f8809cbc43eefbe6079a47f%40riseup.net. For more options, visit https://groups.google.com/d/optout.
