subscription-manager register network error unable to connect to server error: [Errno 110] Connection timed out

Latest response

Hello,

Rhel 6.3 server trying to register with RHN network. All required port and hosts open from firewall as per document https://access.redhat.com/solutions/10818

Ping & telnet to rhn also working fine.
telnet xmlrpc.rhn.redhat.com 443 >>> connecting
telnet xmlrpc.rhn.redhat.com 80 >>> connecting

subscription-manager register --username xxxxxxx --password xxxxx
Network error, unable to connect to server.
Please see /var/log/rhsm/rhsm.log for more information.

Logs file error as below:
15-12-28 10:37:57,124 [INFO] @connection.py:495 - Connection Built: host: subscription.rhn.redhat.com, port: 443, handler: /subscription
2015-12-28 10:38:11,476 [INFO] @connection.py:473 - Using basic authentication as: furqanalam
2015-12-28 10:38:11,477 [INFO] @connection.py:495 - Connection Built: host: subscription.rhn.redhat.com, port: 443, handler: /subscription
2015-12-28 10:38:11,477 [INFO] @managercli.py:777 - Registering as existing consumer: a8da4e4d-1ac5-48e8-a42e-f1f1e83875ec
2015-12-28 10:38:11,478 [DEBUG] @connection.py:306 - Loading CA PEM certificates from: /etc/rhsm/ca/
2015-12-28 10:38:11,478 [DEBUG] @connection.py:288 - Loading CA certificate: '/etc/rhsm/ca/candlepin-stage.pem'
2015-12-28 10:38:11,479 [DEBUG] @connection.py:288 - Loading CA certificate: '/etc/rhsm/ca/redhat-uep.pem'
2015-12-28 10:38:11,479 [DEBUG] @connection.py:327 - Making request: GET /subscription/consumers/a8da4e4d-1ac5-48e8-a42e-f1f1e83875ec
2015-12-28 10:39:14,592 [ERROR] @managercli.py:101 - Error during registration: [Errno 110] Connection timed out
2015-12-28 10:39:14,592 [ERROR] @managercli.py:102 - [Errno 110] Connection timed out

Anyhelp how to fix this issue and connect to RHN network.

Regards,

Attachments

Responses

Were you able to figure this out? I am running into the same issue.

Is there any proxy which could intercept SSL?

I don't have a proxy setup. This is on an aws instance, all outgoing traffic is open & my FWD is turned off.

trying to register the linux server from subscription-manager register , but give an error msg Network error, unable to connect to server. Please see /var/log/rhsm/rhsm.log

when i see /var/log/rhsm/rhsm.log for more information. its says 2017-12-13 11:04:34,503 [ERROR] subscription-manager @managercli.py:160 - Error during registration: [Errno 113] No route to host 2017-12-13 11:04:34,503 [ERROR] subscription-manager @managercli.py:161 - [Errno 113] No route to host

2018-01-19 17:54:13,186 [ERROR] subscription-manager:4104:MainThread @managercli.py:177 - Error during registration: [Errno 110] Connection timed out 2018-01-19 17:54:13,186 [ERROR] subscription-manager:4104:MainThread @managercli.py:178 - [Errno 110] Connection timed out

[root@tst-dcf-rac1 ~]# ping xmlrpc.rhn.redhat.com PING xmlrpc.rhn.redhat.com (209.132.183.192) 56(84) bytes of data. 64 bytes from xmlrpc.rhn.redhat.com (209.132.183.192): icmp_seq=1 ttl=237 time=164 ms 64 bytes from xmlrpc.rhn.redhat.com (209.132.183.192): icmp_seq=2 ttl=237 time=160 ms 64 bytes from xmlrpc.rhn.redhat.com (209.132.183.192): icmp_seq=3 ttl=237 time=163 ms ping is ok

While working on my kickstart files, I ran into this error. The problem was caused by a failure of name resolution, but the root cause was a network misconfiguration in my kickstart file. I had neglected to include the gateway parameter in my network definition. The correct network definition is shown below. I wanted to pass this along in case that's the issue here. Check your kickstart file and make sure the network definition includes all four components, IP address, netmask/prefix, default route gateway, and nameservers. It has been a while, so maybe a non-issue at this point.

Network information network --bootproto=static --device=enp3s0 --ip=10.0.0.51 --netmask=255.255.255.0 --gateway=10.0.0.1 --nameserver=10.0.0.61,10.0.0.1 --onboot=on --ipv6=auto --activate network --hostname=kvmh1.demo.local

I have the same problem and I am able to resolve it just now. I added another network device in my vmware workstation, and i deleted the initial one. On my RHEL 6, i assigned a dhcp through network-config-network-tui. The cause of the issue is DNS resolution. Ensure /etc/resolv.conf is correct