yum fails with "One of the configured repositories failed..."

[Dave C]

One of my template VMs fails to update via `sudo yum upgrade` or even to  `sudo yum install ...`

My vanilla fedora-20-x64 does upgrade as expected.  The one I'm having trouble with is my customized "f20-media" template, on which I've enabled adobe and rpmfusion repos.

I don't doubt that something I've done is at the root of the problem.  I'm still not sure how to solve it.  When I google for these symptoms, I see others have had similar problems, but mostly they seem to have been fixed years ago.  So I'm wondering with qubes specifically how can I workaround this?

Here's how yum starts...

[user@f20-media ~]$ sudo yum update
Loaded plugins: langpacks, post-transaction-actions, refresh-packagekit, yum-
              : qubes-hooks
adobe-linux-x86_64                                          |  951 B  00:00    
fedora/20/x86_64/metalink                                   |  14 kB  00:00    
google-chrome                                               |  951 B  00:00    
qubes-vm-r2-current                                         | 2.9 kB  00:00    
rpmfusion-free                                              | 3.3 kB  00:00    
rpmfusion-free-updates                                      | 3.3 kB  00:00    
rpmfusion-nonfree                                           | 3.3 kB  00:00    
rpmfusion-nonfree-updates                                   | 3.3 kB  00:00    
updates/20/x86_64/metalink                                  |  12 kB  00:00    
updates/20/x86_64/group_gz     FAILED                                          
http://mirrors.syringanetworks.net/fedora/updates/20/x86_64/repodata/6858fd37722f47bb37b289d7b7d11b153305c7c8824a25795fdd42096fdde42b-comps-f20.xml.xz: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
updates/20/x86_64/primary_db   FAILED                                          
http://mirror.web-ster.com/fedora/updates/20/x86_64/repodata/33f4442a503350ab3bf8c236ee87ac94d0dbee255027095105a650ec1eada484-primary.sqlite.xz: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
updates/20/x86_64/group_gz     FAILED                                          

...yum goes on to show similar errors, many times for different mirrors.

At one point mixed into those types of error, it prints this message:

 One of the configured repositories failed (Fedora 20 - x86_64 - Updates),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:

            yum-config-manager --disable updates

     4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=updates.skip_if_unavailable=true

I don't know fedora/yum well enough to understand the implications of the suggested workarounds.  Does anyone here have advice for me?

Thanks, -Dave

[JPL]

Have you tried commenting the metalink line and un-commenting the baseurl line in the fedora repo?
https://ask.fedoraproject.org/en/question/37777/cannot-retrieve-metalink-for-repository-fedora20x86_64/

 

[Dave C]

Thanks for the idea and the link.  I didn't have a chance to try it because strangely, I tried `sudo yum upgrade` one more time, and this time around it simply worked.  I say strangely because I tried repeatedly over about 24 hours before my post here earlier today.  I got the same errors that whole time.  But for whatever reason it is working now.

-Dave

[Jake]

On 05/12/15 23:41, Dave C wrote:

Thanks for the idea and the link.  I didn't have a chance to try it because strangely, I tried `sudo yum upgrade` one more time, and this time around it simply worked.  I say strangely because I tried repeatedly over about 24 hours before my post here earlier today.  I got the same errors that whole time.  But for whatever reason it is working now.

-Dave

i was having a similar problem here with a fresh R2 install - there were problems accessing the yum repos despite the updates proxy being allowed by the vm firewall rules.

after trying several of the suggested fixes in the error message to no avail, i guessed that something was wrong with the qubes update proxy that runs on the netvm. i stopped and started the proxy service with systemctl and all is working now.

i guess this would have also been fixed by a reboot, but i hate to reboot a machine without good cause.

--
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...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/52a87a37-c52f-4fb4-bab6-aa2838da33b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[xim....@gmail.com]

:C ya tienes la solucion?

[Andrew David Wong]

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

On 2016-05-09 10:18, xim....@gmail.com wrote:
> El martes, 12 de mayo de 2015, 10:02:44 (UTC-5), Dave C escribió:
>> One of my template VMs fails to update via `sudo yum upgrade` or
>> even to `sudo yum install ...`
>>
>> My vanilla fedora-20-x64 does upgrade as expected. The one I'm
>> having trouble with is my customized "f20-media" template, on
>> which I've enabled adobe and rpmfusion repos.
>>
>> I don't doubt that something I've done is at the root of the
>> problem. I'm still not sure how to solve it. When I google for
>> these symptoms, I see others have had similar problems, but
>> mostly they seem to have been fixed years ago. So I'm wondering
>> with qubes specifically how can I workaround this?
>>
>> Here's how yum starts...
>>

>> [...]

>>
>> I don't know fedora/yum well enough to understand the
>> implications of the suggested workarounds. Does anyone here
>> have advice for me?
>>
>> Thanks, -Dave
>
> :C ya tienes la solucion?
>

Google translate: "already you have the solution?"

Are you having the same problem as Dave had?

Fedora 20 has been EOL since 2015-06-23. Is your problem with Fedora 23?

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

iQIcBAEBCgAGBQJXMkQ5AAoJENtN07w5UDAw7YYP/1V/846W2iCkI1VILGiLP4tZ
ytGG0w+SkUuvFnapLe9EFdHBmC50N3DjW80BLELkqb6TdBBXC0tumzkB2Pj53POG
MdcfRDCU0QwxX89eWMDZdCIJ1lFKxToZPZYaLDEjmQmwc66F2OPiTambaBSrtr7q
2g2yF7XpIUNussMAycAQv/2FOWwg1SSM0Q9yzDGNP3dYpMjGx6erevRWxe5yt95C
6w05kbR9tSxpaKH/BtV4MxUCoEidq5KcMPgWP0ZGSBz/NhSq8zXmU+7+D3pKpoq0
QO9PdgP6Ih2g/k1O5hquLst2ZH6p83tVvMdqSwhlNc1TqPFjExJP7Rm6UGos8hwA
hpjpzFL4pUuEhgDlmNwl3474UuSN8/ORt1GttAGXDe6STG5RjV/jAs5aElu6KI0k
zX9tlCJGFt9zLKh7w+/1U+29bsyInALh7c+l8QX+JRoCp5GIH690aHmIjB+NoRG4
DMljfnEkxT2e7zmIyCgFLEzyqi7mRsy0hevfBhJzsieRjA8ZlAgbXCwD2CM0Uo/9
J67KMgHrcRlviNd4vMpjmRYlmUpeqVJAWM9ZD0F/mIzCQSvHV/vkQI/m1V0HZ1hM
2gtf5u2E0jZcbNTAOshXTaENqLDgqpxkOnl7v26AjIo9Cy6i3MemFfBzGnPLM3Ci
hrM9HptBOScU9yUTgVrm
=YdvT
-----END PGP SIGNATURE-----