Fedora 23 template not updating - with a blank screen

[48juya+35x...@guerrillamail.com]

Hello,

Since today I'm having problems in updating the fedora 23 template. The update screen seems to hang, showing no info at all. Anyone facing the same issue? How to restore this again into a working condition?

Thank you.

----
Sent using GuerrillaMail.com
Block or report abuse: https://www.guerrillamail.com/abuse/?a=UFR2AB5NVqcQmh2U93EQdRjCStifx8dDiadNcQ%3D%3D

[48juya+35x...@guerrillamail.com]

It seems that doing a 'dnf update --refresh' it provides some output but updating the repositories is taking forever:

[root@fedora-23 ~]# dnf update --refresh
RPM Fusion for Fedora 23 - Nonfree 1.1 MB/s | 156 kB 00:00
RPM Fusion for Fedora 23 - Free 3.8 kB/s | 457 kB 02:00
Qubes OS Repository for VM (updates) 1.0 MB/s | 286 kB 00:00
Fedora 23 - x86_64 - Updates 199 kB/s | 24 MB 02:03

Its hanging for more than 15m now, any ideas how to solve this?

[Jeremy Rand]

48juya+35xih7kuzgagg via qubes-users:

> It seems that doing a 'dnf update --refresh' it provides some output but updating the repositories is taking forever:
>
> [root@fedora-23 ~]# dnf update --refresh
> RPM Fusion for Fedora 23 - Nonfree 1.1 MB/s | 156 kB 00:00
> RPM Fusion for Fedora 23 - Free 3.8 kB/s | 457 kB 02:00
> Qubes OS Repository for VM (updates) 1.0 MB/s | 286 kB 00:00
> Fedora 23 - x86_64 - Updates 199 kB/s | 24 MB 02:03
>
>
> Its hanging for more than 15m now, any ideas how to solve this?

Coincdentally, this occurred to me about 20 minutes ago. Restarting the
fedora-23 TemplateVM and trying to update again fixed it for me. Might
have been a server issue on Fedora's end.

-Jeremy Rand

[48juya+35x...@guerrillamail.com]

I managed to complete the updates after 45m, I followed your suggestion and bounced the template VM and rerun the 'dnf update --refresh' command, however the issue persists - the same painful slowness while fetching the repositories:

[root@fedora-23 ~]# dnf update --refresh

RPM Fusion for Fedora 23 - Free 1.8 MB/s | 457 kB 00:00
RPM Fusion for Fedora 23 - Nonfree - Updates 546 kB/s | 57 kB 00:00
RPM Fusion for Fedora 23 - Free - Updates 0% [ ] --- B/s | 0 B --:-- ETA

[48juya+35x...@guerrillamail.com]

It seems that the updates on dom0 are also affected:

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'...
Checking for dom0 updates...
Last metadata expiration check: 1 day, 16:07:48 ago on Sat Aug 20 22:40:37 2016.
Dependencies resolved.
Nothing to do.
Sending application list and icons to dom0
Complete!
Yum command has been deprecated, redirecting to '/usr/bin/dnf check-update'.
See 'man dnf' and 'man yum2dnf' for more information.
To transfer transaction metadata from yum to DNF, run:
'dnf install python-dnf-plugins-extras-migrate && dnf-2 migrate'

Qubes OS Repository for Dom0 68 MB/s | 151 kB 00:00
Yum command has been deprecated, redirecting to '/usr/bin/dnf -q check-update'.
See 'man dnf' and 'man yum2dnf' for more information.
To transfer transaction metadata from yum to DNF, run:
'dnf install python-dnf-plugins-extras-migrate && dnf-2 migrate'

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Probably just a temporary thing. I was able to update everything a short while
ago with no issues.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXux4jAAoJENtN07w5UDAwK3UQAKts/voKw2CTc9i+PHI8V2Ie
/reVt8GcK08O5mLp2vhhyHfEAVu1qewQ1yEcGGVnYGxhus4T+gJCo4EeMbyRDsJj
qxZ+lV08OkHJ2KhnDe7BVGzbX3evUKmIc4+Ibd0iC/jX4zHACvP/QZiOgM7i/wEx
3PWaM1V1yXAG8vYUsOOIJdW0F4PQs3LMHaaa//IHI6x+5HUGdsuA4tW/PSx9TIuc
pCrNCFCXfuuH7Aj4Fhs7c9eNs5hCerS/O8Ps2lBlFs0d5lsqofD2uBJcnAOzyS/v
xEzzh46t62Pw91HF0Zw97ysI695Fdc7EEfSvlB7Eeg/61ngDMqdOyUA3b3FeN39N
fmmr6H6AZj87e2EqM7TU48/X/2N2k8eyYeV0/gqouvomu2960XBLW5LPWbBbH8DV
Sy70INxL2LzgpPHCOHr2BFe/BBpj/ZMCOsHye3sVZFkg7mhy6ffqs36QRC2S2G0N
1cPaNcVpb57T8/sdAPACFCUGCgrHbupT/v0UVcyJtSkX1th18dXPLemtUAcQ/au+
UD8F3IyBOXnwrEAIrtx2guprlKDamfvZIXv6RhWedCyaCglLVWup6vGannvpFQj8
S+tFYvf3LuTV3UFf5WQfOKHqsdgyAuKKyMs9lQF61u/DyiQ8lElT3E6JPi9b+cy4
PVRmDGyPTo96tuTFU1gP
=U1OP
-----END PGP SIGNATURE-----

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-08-22 05:53, 48juya+35xih7kuzgagg via qubes-users wrote:
> It seems that the updates on dom0 are also affected:
>
> 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'... Checking for dom0 updates... Last metadata expiration
> check: 1 day, 16:07:48 ago on Sat Aug 20 22:40:37 2016. Dependencies
> resolved. Nothing to do. Sending application list and icons to dom0
> Complete!

That doesn't look like normal output from qubes-dom0-update. There should be
no message about sending application list and icons to dom0, since that occurs
in TemplateVMs, not dom0. (It would make no sense for dom0 to "send" something
to itself.) On the other hand, that message is a normal part of a TemplateVM
upgrade.

> Yum command has been deprecated, redirecting to '/usr/bin/dnf
> check-update'. See 'man dnf' and 'man yum2dnf' for more information. To
> transfer transaction metadata from yum to DNF, run: 'dnf install
> python-dnf-plugins-extras-migrate && dnf-2 migrate'
>
> Qubes OS Repository for Dom0
> 68 MB/s | 151 kB 00:00 Yum command has been deprecated, redirecting to
> '/usr/bin/dnf -q check-update'. See 'man dnf' and 'man yum2dnf' for more
> information. To transfer transaction metadata from yum to DNF, run: 'dnf
> install python-dnf-plugins-extras-migrate && dnf-2 migrate'
>

A message stating that dnf would complain about yum being deprecated -- and
that this would be safe to ignore -- should also have been printed in the dom0
terminal in which you issued qubes-dom0-update.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXux7jAAoJENtN07w5UDAwM7EP/1phXy5qRJzhFv74Wo51HvWE
O/FOut8E0kcnGmbXR0PiYdLeBByUR/Rj5YXQoI6N5Eyo3vubPsc3lp2SQnuBzdL8
jFy09xwGwZzWgVGO671MF1OMJHiX2ESvjga0hZJsDeVJdDTty+rnaxL0Ps8yQt16
EpiAATNr7xaOdrRcax6jzUrkpJrY+c7CYEmalDsGG+DaqEFJRBT0OudM0GHUsd6o
qAZ3AWunA2ufweyoUdm+MoF0ydcacVHQ+QTx/Wk/KNPAez+3sfNbV0ZvRJFaHQS2
weSpxvJKfNYmlC9S6P7amAA4L8wKDUR2cNOR7qwtRXjtYzPKGaMgAIG2XzUrvn37
GvBtsjQ5d2RCJvmHdDs5kEyJKd+EiBEC8K0NxEl0nYSgwr9zMAdZzHnNMIFWVAqk
e+1OjRF8U3VWZmngJr6oGWKa7AO8IOyPbsYOmTJdrJ4OE/fXTRhnaAibLMMsIyeo
Z2pQSO2koNrH7h4T9iIJZA46rZ/c0twQkP1RWk77yellncl+8SKXc764KVQFG8Rd
IflnZRnz8R5s+b91ksYibFZTsjC6ZOStZq1b0TQuIY/ajAnqZyvgJ5gWnrFIibQz
gcZWZVe8vyi0QAy1owMtJ2pbbeMkYYq4+9TJ9krMj3H7lG/fBeX+WOnTBlyidctE
604xIMgkN5ZDNfHx+pRO
=nJDt
-----END PGP SIGNATURE-----

[48kc5j+2yh...@guerrillamail.com]

>Probably just a temporary thing. I was able to update everything a short while
>ago with no issues.

Unfortunately it doesn't seem to be temporarily, the updade for the fedora23 template is still hanging. I honest don't think this is normal or due to some problems with the yum repos.
Any idea what I can do to solve this huge latency?

>That doesn't look like normal output from qubes-dom0-update. There should be
>no message about sending application list and icons to dom0, since that occurs
>in TemplateVMs, not dom0. (It would make no sense for dom0 to "send" something
>to itself.) On the other hand, that message is a normal part of a TemplateVM
>upgrade.

Apparently that was caused since I run the upgrade of dom0 while I was upgrading the fedora23 template at the same time. Dunno if this is the cause, but could possibly affect it.
If this isn't the normal behavior, how can this be corrected then?

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-08-22 09:02, 48kc5j+2yh9dxa25wb0o via qubes-users wrote:
>> Probably just a temporary thing. I was able to update everything a short
>> while ago with no issues.
>
> Unfortunately it doesn't seem to be temporarily, the updade for the
> fedora23 template is still hanging. I honest don't think this is normal or
> due to some problems with the yum repos. Any idea what I can do to solve
> this huge latency?
>

Are you downloading updates over Tor (sys-whonix) or clearnet?

Persistent slow/hanging downloads over Tor could be due to a bad entry guard(s).

>
>> That doesn't look like normal output from qubes-dom0-update. There
>> should be no message about sending application list and icons to dom0,
>> since that occurs in TemplateVMs, not dom0. (It would make no sense for
>> dom0 to "send" something to itself.) On the other hand, that message is a
>> normal part of a TemplateVM upgrade.
>
> Apparently that was caused since I run the upgrade of dom0 while I was
> upgrading the fedora23 template at the same time. Dunno if this is the
> cause, but could possibly affect it. If this isn't the normal behavior, how
> can this be corrected then?
>

That would explain it. If you were running with --pass-io, then there would be
text from both.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXuy/dAAoJENtN07w5UDAwcZUP/RC0AjhE8FhbGewNEVeHfir9
UDWuykf/EnHY9Wh0bFYfTsh8ho/5Lm5UohI+uz22kZNwYOVwTFzI/WGaWwT4+pYu
cgbqSPhcWqL3p8WxucFhCmiGhAu9PLTNKngqYPnjrjUR2wlnyJaw1w7dhn55Q4IT
Mne/6OYBHPitAXd1DsbPUcmuV3gGF8+L5ELPYY+uJvvJG/w2Po6Pz3V5OIcJhNe5
hU24UFMC8Fo6+rs41rEICzcGwTDnhN8HhGBIvqxAIWjvC7HJIWHwcqtbMc4EO9gG
OHtIJ+2+M6HuPpfz4heo+lyl158Bjf9j+A3e13jqI9KIMFL7n7vldNwNDbwgRXLc
dnMIGt/hnnotnwTraISuduq5VRU8yCHbOpEE6ChTkybI12eP2Nj7/g0XApYuD/ZN
p35v5zauUyjvSKE00jcPR6Squ4eVn9+rQ0Ulgbo6jBok3CAlPXefv0QDm5nOO47s
r7ucvihnJ4mwHJEPHvnQIJQjAghe1bXl9kIwtjnHn0//2o2Ql8GMX1yE112qZpdQ
6qyng37Bv+vArdfk9mFHwCPmCoJ91rnv5NTvk1qnyWD0/TP0cA//hR/PrMI1wIwm
z52HcAAfnT/A8npn5AdgTeIJAg+R8Bor6PumNIPsU7GPo81mqyaUn0Olh24+pqQS
Z8gY2AuQYgxlFe4AKZwi
=WB/Q
-----END PGP SIGNATURE-----

[48krcr+coa...@guerrillamail.com]

>Are you downloading updates over Tor (sys-whonix) or clearnet?
>Persistent slow/hanging downloads over Tor could be due to a bad entry guard(s).

Clearnet, is not a bandwidth problem the update on all the other templates are working just fine its only on fedora23 that this is taking forever.

>That would explain it. If you were running with --pass-io, then there would be
>text from both.

Both were running at the same time just once. This output from dom0 was taken when the dom0 was updating alone without any other updating taking place. Although I suspect the problem was originated when both updates were running concurrently and now everytime I run the dom0 updates I get this message. I believe something might have caused this behavior when both updates were triggered simultaneously.