[tools] [patch] EL5 aka 5Server

[Oliver Falk]

On 03/27/2007 09:49 AM, Dag Wieers wrote:
> On Tue, 27 Mar 2007, Oliver Falk wrote:
> 
>> On 03/27/2007 09:36 AM, Dag Wieers wrote:
>>
>>> I have problems using then rhn-tools channel. It could not subscribe
>>> automatically and when I subscribed the mrepo-systemid's on the RHN website
>>> to the rhn-tools channel, I get the following respons when updating:
>>>
>>>  rhel5s-i386: Updating Red Hat Enterprise Server 5 (i386)
>>>  rhel5s-i386: Mirror packages from rhns://rhn-tools-rhel-i386-server-5 to
>>>  /shelf/redhat/system/rhel5s-i386/rhn-tools
>>>  rhnget: [('SSL routines', 'SSL23_WRITE', 'ssl handshake failure')]
>>>  mrepo: Mirroring failed for rhns://rhn-tools-rhel-i386-server-5 with
>>>  message:
>>>    Failed with return code: 256
>>>  rhel5s-x86_64: Updating Red Hat Enterprise Server 5 (x86_64)
>>>  rhel5s-x86_64: Mirror packages from rhns://rhn-tools-rhel-x86_64-server-5
>>>  to /shelf/redhat/system/rhel5s-x86_64/rhn-tools
>>>  rhnget: [('SSL routines', 'SSL23_WRITE', 'ssl handshake failure')]
>>>  mrepo: Mirroring failed for rhns://rhn-tools-rhel-x86_64-server-5 with
>>>  message:
>>>    Failed with return code: 256
>>>
>>> This is the same error for doing the rhn-tools channel subscription.
>>>
>>> I do not understand why one of the channels behaves like this consistently
>>> and can only assume this is a RHN error (or maybe something weird with the
>>> proxy ?).
>>>
>>> Can someone verify this ?
>> Config-Line:
>> rhn-tools = rhn:///$repo-rhel-$arch-server-$release
>>
>> I didn't include it in my config, but now did for testing and it seems to
>> work:
>>
>> <snip>
>> rhel5Server-i386: Updating Red Hat 5 Server (i386)
>> rhel5Server-i386: Mirror packages from rhn:///rhn-tools-rhel-i386-server-5 to
>> /var/depo/rhel5Server-i386/rhn-tools
>> auto-kickstart-1.13-2.el5.n ########################## Done. 
>> auto-kickstart-ks-redhat-ad ########                   305 k/sec, 00:00:08
>> rem.
>> </snap>
>>
>> Maybe only some sort for short outage on rhn!?
> 
> Well, I had it yesterday as well and other channels are not affected. 
> Since you are using RHN and not RHNS, I tried using without SSL instead, 
> and that gives me:
> 
> 	rhel5s-i386: Mirror packages from rhn://rhn-tools-rhel-i386-server-5 to /shelf/redhat/system/rhel5s-i386/rhn-tools
> 	Traceback (most recent call last):
> 	  File "/usr/bin/rhnget", line 498, in ?
> 	    main()
> 	  File "/usr/bin/rhnget", line 477, in main
> 	    mirrorrhn(op.uri, op.destination)
> 	  File "/usr/bin/rhnget", line 346, in mirrorrhn
> 	    systemid = rhnlogin(url, path)
> 	  File "/usr/bin/rhnget", line 313, in rhnlogin
> 	    li = rpcServer.doCall(server.up2date.login, systemid)
> 	  File "/usr/share/rhn/up2date_client/rpcServer.py", line 307, in doCall
> 	    raise up2dateErrors.CommunicationError(e.errmsg)
> 	up2date_client.up2dateErrors.CommunicationError: Error communicating with server. The message was:
> 	Not Found
> 	mrepo: Mirroring failed for rhn://rhn-tools-rhel-i386-server-5 with 
> 	message:
> 	  Failed with return code: 256
> 
> Which makes no sense either. I don't understand it works for you and not 
> for me :)

And this?:
rhnget -vvvv -n --release=5Server 
--systemid=/var/depo/rhel5Server-i386/systemid 
rhn:///rhn-tools-rhel-i386-server-5 /tmp

-of