[tools] mrepo up2date registration problem...

[Pienaar, Derek]

Hi there,

We are still getting the same error, even after setting configuring
proxy settings in /etc/profile.d/proxy.sh.
I have tested with yum, and proxy access is working. I am however also
aware that proxy settings can be
specified in the up2date tool as well.

Is there a preference to which proxy settings are used? 

... Stil getting same error ...

Traceback (most recent call last):
  File "/usr/bin/gensystemid", line 244, in ?
    main()
  File "/usr/bin/gensystemid", line 210, in main
    systemid = rpcServer.doCall(s.registration.new_user, op.rhnusername,
op.rhnpassword)
  File "/usr/share/rhn/up2date_client/rpcServer.py", line 236, in doCall
    ret = apply(method, args, kwargs)
  File "/usr/lib/python2.3/xmlrpclib.py", line 1029, in __call__
    return self.__send(self.__name, args)
  File "/usr/share/rhn/up2date_client/rpcServer.py", line 46, in
_request1
    ret = self._request(methodname, params)
  File "/usr/lib/python2.3/site-packages/rhn/rpclib.py", line 319, in
_request
    request, verbose=self._verbose)
  File "/usr/lib/python2.3/site-packages/rhn/transports.py", line 168,
in
request
    headers, fd = req.send_http(host, handler)
  File "/usr/lib/python2.3/site-packages/rhn/transports.py", line 694,
in
send_http
    self._connection.connect()
  File "/usr/lib/python2.3/site-packages/rhn/connections.py", line 244,
in
connect
    response = HTTPConnection.getresponse(self)
  File "/usr/lib/python2.3/site-packages/rhn/connections.py", line 143,
in
getresponse
    response.begin()
  File "/usr/lib/python2.3/site-packages/rhn/connections.py", line 217,
in
begin
    HTTPResponse.begin(self)
  File "/usr/lib/python2.3/httplib.py", line 273, in begin
    version, status, reason = self._read_status()
  File "/usr/lib/python2.3/httplib.py", line 237, in _read_status
    raise BadStatusLine(line)
httplib.BadStatusLine

What is also funny, although proxy.sh settings take effect, and can be
successfully used wih yum, when I use the links browser, and try to
browse to http://xmlrpc.rhn.redhat.com/XMLRPC as recommended, I get
a connection refused?

Is the links' browser proxy setting set somewhere else?

Thanks!

DP.

 
-----Original Message-----
From: Dag Wieers [mailto:dag at wieers.com] 
Sent: 09 October 2007 12:47 PM
To: Pienaar, Derek
Subject: RE: [tools] mrepo up2date registration problem...

On Tue, 9 Oct 2007, Pienaar, Derek wrote:

> Is it possible that it might be related to the OS being Centos?

No, it should not make a difference, if you have followed the
instructions
from the documentation.


> -----Original Message-----
> From: Dag Wieers [mailto:dag at wieers.com]
> Sent: 09 October 2007 12:05 PM
> To: Pienaar, Derek
> Cc: tools at lists.rpmforge.net
> Subject: Re: [tools] mrepo up2date registration problem...
>
> On Tue, 9 Oct 2007, Pienaar, Derek wrote:
>
> > I have a centos 4.3 server that I am configuring as an mrepo server
> for
> > the rest of
> >
> > my centos and rhel servers. At first I had trouble with the standard
> > up2date package/tool that
> >
> > came with the stock centos 4.3 installation.
> >
> >
> >
> > I found more info online: I removed the "centos" up2date package,
and
> > install an up2date
> >
> > Package from an rhel distribution. (Same version.)
> >
> >
> >
> > I have also configured the proxy settings in up2date, but without
> luck.
> > My problem is that
> >
> > when I run gensystemid as follows:
> >
> >
> >
> > gensystemid -u rhnuser -p rhnpassword -r 4ES -a i386
> > /var/www/mrepo/rh4es-i386
> >
> >
> >
> > I get the following error:
> >
> >
> >
> > Traceback (most recent call last):
> >
> >   File "/usr/bin/gensystemid", line 244, in ?
> >
> >     main()
> >
> >   File "/usr/bin/gensystemid", line 210, in main
> >
> >     systemid = rpcServer.doCall(s.registration.new_user,
> op.rhnusername,
> > op.rhnpassword)
> >
> >   File "/usr/share/rhn/up2date_client/rpcServer.py", line 236, in
> doCall
> >
> >     ret = apply(method, args, kwargs)
> >
> >   File "/usr/lib/python2.3/xmlrpclib.py", line 1029, in __call__
> >
> >     return self.__send(self.__name, args)
> >
> >   File "/usr/share/rhn/up2date_client/rpcServer.py", line 46, in
> > _request1
> >
> >     ret = self._request(methodname, params)
> >
> >   File "/usr/lib/python2.3/site-packages/rhn/rpclib.py", line 319,
in
> > _request
> >
> >     request, verbose=self._verbose)
> >
> >   File "/usr/lib/python2.3/site-packages/rhn/transports.py", line
168,
> > in request
> >
> >     headers, fd = req.send_http(host, handler)
> >
> >   File "/usr/lib/python2.3/site-packages/rhn/transports.py", line
694,
> > in send_http
> >
> >     self._connection.connect()
> >
> >   File "/usr/lib/python2.3/site-packages/rhn/connections.py", line
> 244,
> > in connect
> >
> >     response = HTTPConnection.getresponse(self)
> >
> >   File "/usr/lib/python2.3/site-packages/rhn/connections.py", line
> 143,
> > in getresponse
> >
> >     response.begin()
> >
> >   File "/usr/lib/python2.3/site-packages/rhn/connections.py", line
> 217,
> > in begin
> >
> >     HTTPResponse.begin(self)
> >
> >   File "/usr/lib/python2.3/httplib.py", line 273, in begin
> >
> >     version, status, reason = self._read_status()
> >
> >   File "/usr/lib/python2.3/httplib.py", line 237, in _read_status
> >
> >     raise BadStatusLine(line)
> >
> > httplib.BadStatusLine
> >
> > ##################################################################
> >
> >
> >
> > What is causing this? I have searched for info, but to no avail.
>
> What happens if you try to go to the URL ?
>
> 	http://xmlrpc.rhn.redhat.com/XMLRPC
>
> Is it possible you should be using a proxy server or that it needs to
be
> socksified ?
>
>

-- 
--   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]
To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: 
https://www.fnb.co.za/disclaimer.html 

If you are unable to access the Disclaimer, send a blank e-mail to
firstrandbankdisclaimer at fnb.co.za and we will send you a copy of the Disclaimer.