killolotus.blogg.se

Repo Name: Red Hat CloudForms Tools for RHEL 6 (RPMs) Repo Name: Red Hat Enterprise Linux 6 Server (RPMs) # date & subscription-manager -proxy=:3128 repos -listĮntitled Repositories in /etc//redhat.repo # date & subscription-manager -proxy=:3128 list -consumed Product Name: Red Hat Enterprise Linux Server # date & subscription-manager -proxy=:3128 subscribe -auto ProductName: Red Hat Enterprise Linux Server, Self-support (1-2 sockets) # date & subscription-manager -proxy=:3128 list -available

* Proxy auth using Basic with user 'username' * About to connect() to proxy port 8080 (#0) The communication is not properly established with the correct certificates: # curl -v -proxy-user user:password -proxy :8080 -cacert /etc/rhsm/ca/redhat-uep.pem When using a http proxy with RHSM, the proxy settings need to be put in /etc/rhsm/nf (and not /etc/yum.conf).Ĭheck if a system is using standard curl package from Red Hat.Īdditional information: RHSM Subscription Issues Troubleshooting Do's and Don'ts Root Cause or- # subscription-manager attach -pool=POOLID

If the UUID does not match, refresh the subscription data from system: # subscription-manager refresh Then enter the system's UUID in the filter box to see if it matches. Check the system's UUID on the Customer Portal: Go to -> Subscriptions -> Systems (under the subheading Subscriber Inventory) or open.Get the UUID from the system: # openssl x509 -in /etc/pki/consumer/cert.pem -noout -text| grep 'Subject: CN' Sometimes proxies are configured to resign SSL communication (similar to man-in-the-middle attack).Ĭrosscheck if UUID of system matches on the Customer Portal: Check if a proxy (or anything between the server and Red Hat) is not changing the SSL certificate.: problem making ssl connectionĮrror: Cannot retrieve repository metadata (repomd.xml) for repository: rhel-6-server-cf-tools-1-rpms. Loaded plugins: downloadonly, product-id, subscription-manager

Let's troubleshoot this error for example: # yum check-update In general, this can help solve many errors. The following steps can be used for basic troubleshooting on subscription-manager and yum issues.