Bug 117009 - up2date cannot register via proxy
up2date cannot register via proxy
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: up2date (Show other bugs)
3.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Fanny Augustin
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-02-27 07:32 EST by Mindaugas Riauba
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-05-11 23:47:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mindaugas Riauba 2004-02-27 07:32:22 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
If I try to register my new machine using proxy I'm getting the following error:
Traceback (most recent call last):
  File "/usr/sbin/up2date", line 1190, in ?
    sys.exit(main() or 0)
  File "/usr/sbin/up2date", line 720, in main
    tui.main()
  File "tui.py", line 1097, in main
  File "tui.py", line 1041, in run
  File "tui.py", line 613, in __init__
  File "hardware.py", line 517, in Hardware
  File "hardware.py", line 345, in read_network
  File "hardware.py", line 320, in findHostByRoute
socket.error: (111, 'Connection refused')


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

How reproducible:
Always

Steps to Reproduce:
1. up2date --register

Expected Results:  Registration

Additional info:

Fixed by editing /usr/share/rhn/up2date_client/hardware.py line 320. 
Changed 80 to 3128 (my proxy port).
Comment 1 Adrian Likins 2004-03-12 14:29:34 EST
fixed in 4.2.8
Comment 2 John Flanagan 2004-05-11 23:47:36 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2004-138.html

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