Ask Your Question

404 File Not Found on yum repo? [closed]

asked 2015-11-24 13:22:27 -0500

RCMMike gravatar image

updated 2015-11-24 15:24:35 -0500

I'm running CentOS Linux release 7.1.1503 (Core) and attempting to install Puppet Server. I've tried using both the puppetlabs-release and puppetlabs-release-PC1 repos, with both giving the same errors when I do anything with yum:

puppetlabs-products/x86_64/pri FAILED                                  [Errno 14] HTTP Error 404 - Not Found
Trying other mirror. [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.

 One of the configured repositories failed (Puppet Labs Products El 7 - x86_64),
 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 puppetlabs-products

     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

            yum-config-manager --save --setopt=puppetlabs-products.skip_if_unavailable=true

failure: repodata/f50e7be5aa9640379294fb6cef7ee54d4d93d186-primary.sqlite.bz2 from puppetlabs-products: [Errno 256] No more mirrors to try. [Errno 14] HTTP Error 404 - Not Found

I've also tried yum clean metadata, yum clean all, as well as removing and readding the repos. It's doing the same thing on multiple machines, including a server I already had the repo previously working on.

Any ideas?

EDIT: There's an unplanned outage right now of the Puppet repo servers.

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by RCMMike
close date 2015-11-24 15:24:53.296187


Having the exact same issue on brand new CentOS 7 instances (EC2 and local vagrant boxes). This is not an issue of bad cache data on the local machines (these are brand new instances). As the OP states, running yum clean metada, yum clean dbcache or yum clean all changes nothing.

ericwestfall gravatar imageericwestfall ( 2015-11-24 14:37:59 -0500 )edit

12 Answers

Sort by ยป oldest newest most voted

answered 2015-11-24 14:24:36 -0500


repomd.xml for the repo does not report the correct primary, or the primary db has not been copied in. createrepo needs to be rerun.



edit flag offensive delete link more

answered 2015-11-24 14:00:31 -0500

Looks like repo may be incorrect..try

rpm -ivh

As root. Then try and install puppet again

Cheers Stuart

edit flag offensive delete link more


That's the one that I did install. I just tried reinstalling and running yum install puppetserver, and no dice: [Errno 14] HTTP Error 404 - Not Found

RCMMike gravatar imageRCMMike ( 2015-11-24 14:28:10 -0500 )edit
sahumphries gravatar imagesahumphries ( 2015-11-24 15:03:16 -0500 )edit

answered 2015-11-24 15:06:42 -0500

For what it's worth, if you browse the repo data you can see the mirror is pointing to a file (f50e7be5aa9640379294fb6cef7ee54d4d93d186-primary.sqlite.bz2) that no longer exists. The only sqlite files present in the repodata are:

c9ca1f9ffb300a40471fa2aa933872f414bd3a73-filelists.sqlite.bz2 e5acd1d348719265c52e35044642c6583acf28ba-other.sqlite.bz2 7e8e35463e51ebaa8173b9d617238e0a96e19673-primary.sqlite.bz2

The repomd.xml file has the primary_db set to a non-existent file:

<data type="primary_db">
<checksum type="sha">f50e7be5aa9640379294fb6cef7ee54d4d93d186</checksum>
<open-checksum type="sha">35af9e4e0bd36283228c57087a45e261e927d9cd</open-checksum>
<location href="repodata/f50e7be5aa9640379294fb6cef7ee54d4d93d186-primary.sqlite.bz2"/>


Puppetlabs - please fix the bad references in the repomd.xml file to return the repository to working order :-)

edit flag offensive delete link more

answered 2015-11-24 15:15:14 -0500

I'm having the same issue. Maybe just need to recreate the repository:

puppetlabs-pc1/x86_64/filelist FAILED                                  [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
(11/23): extras/7/x86_64/other_db                                | 417 kB  00:00:00     
(12/23): extras/7/x86_64/primary_db                              | 117 kB  00:00:00     
puppetlabs-pc1/x86_64/primary_ FAILED                                  [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
puppetlabs-pc1/x86_64/other_db FAILED                                  [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
edit flag offensive delete link more

answered 2015-11-24 13:32:02 -0500

DMAeaton gravatar image

This is impacting us as well. Looks like the repodata.xml was updated on 11/19, but the primary db is still from 11/17

edit flag offensive delete link more

answered 2015-11-24 14:29:52 -0500

The repo is broken (xml file):

<data type="primary"><checksum type="sha">ae9b7dbd2b5b0a662ad3009dbfa867abf081d293</checksum><open-checksum type="sha">39b0b4d67208a4e66c6cdb524fc4a977d57ada4b</open-checksum><location href="repodata/ae9b7dbd2b5b0a662ad3009dbfa867abf081d293-primary.xml.gz"/><timestamp>1447972987</timestamp><size>53491</size><open-size>1043576</open-size></data>

edit flag offensive delete link more

Question Tools



Asked: 2015-11-24 13:22:27 -0500

Seen: 1,702 times

Last updated: Nov 24 '15