Enabling repository on Red Hat Satellite 6 fails with error: SL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A

Environment

• Red Hat Satellite 6.x

Issue

• SL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A
• Enabling repository on Satellite fails.

Resolution

• Verify if a proxy is configured on Satellite and which requires authentication.

    # cat /etc/rhsm/rhsm.conf | grep -i proxy
  

• Using the curl command we can verify the connectivity.

    # curl -vvv --proxy proxy.example.com:8080 https://cdn.redhat.com --cacert /etc/rhsm/ca/redhat-uep.pem"
    # curl -vvv --proxy proxy.example.com:8080 subscription.rhsm.redhat.com --cacert /etc/rhsm/ca/redhat-uep.pem"
  

For more KB articles/solutions related to Red Hat Satellite 6.x Repository Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x Repository Issues.

Root Cause

• Repo was not getting enabled as proxy was defined which requires authentication.

• Output as per the curl command.

    > GET HTTP://subscription.rhsm.redhat.com/ HTTP/1.1
    > User-Agent: curl/7.29.0
    > Host: subscription.rhsm.redhat.com
    > Accept: */*
    > Proxy-Connection: Keep-Alive
    >
    < HTTP/1.1 407 Proxy Authentication Required
  

Diagnostic Steps

• Errors as per /var/log/messages

    Feb 10 10:30:14 srdzzapp0492 goferd: [ERROR][worker-0] gofer.threadpool:100 - ModelError: Connection 
    amqps://subscription.rhsm.redhat.com:5647 timed out: Opening connection
  

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.