I had an invalid certificate and up2date bomb out. Here is a traceback: Traceback (innermost last): File "/usr/sbin/up2date", line 1169, in ? main() File "/usr/sbin/up2date", line 254, in main up2date.updateLoginInfo() File "/usr/share/rhn/up2date_client/up2date.py", line 556, in updateLoginInfo loginInfo = login() File "/usr/share/rhn/up2date_client/up2date.py", line 487, in login loginInfo = doCall(server.up2date.login, systemId) File "/usr/share/rhn/up2date_client/up2date.py", line 426, in doCall ret = apply(method, args, kwargs) File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 689, in __call__ return self.__send(self.__name, args) File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 746, in __request self.__protocol File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 652, in request return self.parse_response(fd) File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 667, in parse_response return u.close() File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 366, in close raise apply(Fault, (), self._stack[0]) xmlrpclib.Fault: <Fault -9 """ Error Message: Please run rhn_register as root on this client Error Class Code: 9 Error Class Info: Invalid Server Certificate.
Sounds as if you don't have a certificate at all on that machine. The message which is getting returned is to run 'rhn_register' on the machine to register it with RHN. Have you done that?
After I run rhn_register everything was ok. I saved traceback because up2date should write error message more cleanly than bomb out.
current releases should be better behaved.