Bug 113483 - rhn_register errors when specifying a satellite server
rhn_register errors when specifying a satellite server
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: rhn_register (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Fanny Augustin
Depends On:
  Show dependency treegraph
Reported: 2004-01-14 09:29 EST by Jody Steadman
Modified: 2007-11-30 17:06 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-02 15:57:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jody Steadman 2004-01-14 09:29:49 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922

Description of problem:
Traceback (innermost last):
  File "/usr/sbin/rhnreg_ks", line 326, in ?
  File "/usr/sbin/rhnreg_ks", line 289, in main
    hardwareList = hardware.Hardware()
  File "/usr/share/rhn/register/hardware.py", line 375, in Hardware
    ret = read_network()
  File "/usr/share/rhn/register/hardware.py", line 297, in read_network
    hostname, ipaddr = findHostByRoute()
  File "/usr/share/rhn/register/hardware.py", line 274, in findHostByRoute
    s.connect((server, 80))
socket.error: (113, 'No route to host')

Printing the server variable in findHostByRoute() shows
xmlrpc.rhn.redhat.com as the server even when a different server is
specified in the files /etc/sysconfig/rhn/up2date and

Placing an entry for xmlrpc.rhn.redhat.com in /etc/hosts (pointing to
the satellite server IP address) allows the registration process to

Adrian assisted with the debugging.

Version-Release number of selected component (if applicable):

How reproducible:
Didn't try

Additional info:
Comment 1 Adrian Likins 2004-09-02 15:57:20 EDT
This should be fixed with rhel2.1-u5 (rhn_register-2.9.12,

Note You need to log in before you can comment on or make changes to this bug.