[tools] [patch] EL5 aka 5Server

[John Scherff]

I did the same #&$*# thing (minus a slash).  Took me half a day and 100
curses against Red Hat before I figured it out.

-----Original Message-----
From: tools-bounces at lists.rpmforge.net
[mailto:tools-bounces at lists.rpmforge.net] On Behalf Of Dag Wieers
Sent: Tuesday, March 27, 2007 1:02 AM
To: Oliver Falk
Cc: tools at lists.rpmforge.net
Subject: Re: [tools] [patch] EL5 aka 5Server

On Tue, 27 Mar 2007, Oliver Falk wrote:

> 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

That works and after investigation, I was missing a slash in rhns:///

You know what I am thinking now ? We have a great community when the 
developer has to ask the community for support :)

On the other hand, if I'm making this mistake we should have something
to 
make sure people cannot make the same mistake again.

Thanks again, Oliver !
--   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
[all I want is a warm bed and a kind word and unlimited power]
_______________________________________________
tools mailing list
tools at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/tools