Hide Forgot
The following was filed automatically by firstboot: firstboot 1.110.8 exception report Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/firstboot/interface.py", line 105, in _nextClicked self.advance() File "/usr/lib/python2.6/site-packages/firstboot/interface.py", line 148, in advance result = module.apply(self, self.testing) File "/usr/share/rhn/up2date_client/firstboot/rhn_login_gui.py", line 63, in apply rhnregGui.try_to_activate_hardware() File "/usr/share/rhn/up2date_client/rhnregGui.py", line 1372, in try_to_activate_hardware code = rhnreg._activate_hardware(username, password) File "/usr/share/rhn/up2date_client/rhnreg.py", line 612, in _activate_hardware login, password, hardwareInfo) File "/usr/share/rhn/up2date_client/rhnreg.py", line 643, in activateHardwareInfo hardwareInfo, other) File "/usr/share/rhn/up2date_client/rhnserver.py", line 50, in __call__ return rpcServer.doCall(method, *args, **kwargs) File "/usr/share/rhn/up2date_client/rpcServer.py", line 277, in doCall raise up2dateErrors.CommunicationError(e.errmsg) CommunicationError: Error communicating with server. The message was: Service Temporarily Unavailable
Created attachment 486571 [details] File: backtrace
CommunicationError: Error communicating with server. The message was: Service Temporarily Unavailable This is something we cannot fix in the RHEL RHN Client. If the RHN Hosted services are down, they are down, all we can do is report this to the client. Regards, Cliff