Unable to see custom EPEL mirror from clients

Latest response

Hi -hoping someone can help me with an issue that has got me baffled. I've recently built a Satellite 6.2.5 server that I'm trying to a add a custom product to - namely EPEL. So I've added the product and GPG key as per knowledge base article and the product has fully sync'd.

I can see that the product is published at http://server-name/pulp/repos/QA/Library/custom/EPEL7Server/EPEL7Server/ and from the client if I do a:

wget http://server-name/pulp/repos/QA/Library/custom/EPEL7Server/EPEL7Server/repodata/repomd.xml the page is retrieved almost instantly.

If I add the following to /etc/yum.repos.d/epel.repo:

[EPEL]
name=EPEL for RHEL 7 $releasever - $basearch
baseurl=http://servername/pulp/repos/QA/Library/custom/EPEL7Server/EPEL7Server/
enabled=1

And then try a yum install ... I just get this back:

http://server-name/pulp/repos/QA/Library/custom/EPEL7Server/EPEL7Server/repodata/repomd.xml: [Errno 12] Timeout on http://server-name/pulp/repos/QA/Library/custom/EPEL7Server/EPEL7Server/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 60 seconds')
Trying other mirror.

And this is repeated a number of times before finally failing, I've tried the manual test countless times - its not a network issue. Has anyone any ideas, maybe I'm missing something really obvious here but just can't make sense of whats wrong.

Thanks - Julian.

Responses

Oh, should have said I have also imported the GPG key from https://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-7Server

And added to the client.

Hi,

try to run the yum with strace to see where it takes so long...

//Zdenek

OK, so ran a strace yum update and tbh it didn't really tell me much that I understood!! There was nothing obvious I could pick out, I'd paste the result in to here but I tried that and the results were pretty terrible to view.

For example I see this repeated:

poll([{fd=8, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 0) = 0 (Timeout)

poll([{fd=8, events=POLLIN}], 1, 1000) = 0 (Timeout)

And then this:

write(2, "http://server-name."..., 325http://server-name/pulp/repos/QA/Library/custom/EPEL7Server/EPEL7Server/repodata/repomd.xml: [Errno 12] Timeout on http://server-name/pulp/repos/QA/Library/custom/EPEL7Server/EPEL7Server/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 10 seconds') ) = 325

write(2, "Trying other mirror.\n", 21Trying other mirror. ) = 21

Ok I've removed the actual server name, but if I try the url from the server itself with a wget it works instantly. I think the operation to slow is a red herring here.

The RHEL mirrors are working perfectly fine, just the EPEL mirror / product I'm trying to add.

Beginning to lose my patience with this now ;-) Randomly checking things I've already checked and probably have no bearing on this at all.

With the EPEL repo enabled on the client by way of yum-config-manager --enable EPEL all I see in the foreman-ssl_access_ssl.log on the Satellite server is:

10.152.216.40 - 6f6b5528-a9c3-4609-8d63-6c1e2ef4b5c0 [20/Dec/2016:11:24:47 +0000] "GET /rhsm/ HTTP/1.1" 200 1746 "-" "RHSM/1.0 (cmd=yum)"

10.152.216.40 - 6f6b5528-a9c3-4609-8d63-6c1e2ef4b5c0 [20/Dec/2016:11:24:47 +0000] "GET /rhsm/consumers/6f6b5528-a9c3-4609-8d63-6c1e2ef4b5c0/content_overrides HTTP/1.1" 200 2 "-" "RHSM/1.0 (cmd=yum)"

10.152.216.40 - 6f6b5528-a9c3-4609-8d63-6c1e2ef4b5c0 [20/Dec/2016:11:24:47 +0000] "GET /rhsm/consumers/6f6b5528-a9c3-4609-8d63-6c1e2ef4b5c0/release HTTP/1.1" 200 19 "-" "RHSM/1.0 (cmd=yum)"

Which I assume is normal and nothing else apart from this on the client:

failure: repodata/repomd.xml from EPEL: [Errno 256] No more mirrors to try.

http://server-name/pulp/repos/QA/Library/custom/EPEL7Server/EPEL7Server/repodata/repomd.xml: [Errno 12] Timeout on http://server-name/pulp/repos/QA/Library/custom/EPEL7Server/EPEL7Server/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 5 seconds')

Okey dokey, so I've managed to get this working. The errors are super misleading and gave me absolutely no idea as to why it was failing. The EPEL product was added per the RHEL knowledge base article on adding custom content. It was not associated with any content view or activation key - I just added a epel.repo file to the client as I would normally do. So this is what I did:

Edited the RHEL7 content view and added the EPEL7 product to the Yum Content and published a new version - I could now see all the RHEL & EPEL packages were contained in the single view.

I then edited the activation key and made sure it referred to the content view above - it did. I then set the Auto-Attach to NO and under the subscriptions tab manually selected ALL the products listed.

On the client I then ran the following commands:

subscription-manager register --org="QA" --activationkey="QA" --force

subscription-manager refresh

subscription-manager repos

And the result is what I wanted all along, I see Red Hat Enterprise Linux 7 Server (RPMs), Red Hat Satellite Tools 6.2 (for RHEL 7 Server) (RPMs) & EPEL7Server.

Thanks.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.