Bug 73081
Summary: | up2date can get server too busy error mid-session | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michael Young <m.a.young> | ||||
Component: | up2date | Assignee: | Adrian Likins <alikins> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jay Turner <jturner> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 8.0 | CC: | gafton, grover, mihai.ibanescu, rm.riches, srevivo, stk | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2004-01-12 12:55:50 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Michael Young
2002-08-30 14:16:00 UTC
yes, investigating... server guys claim it shouldnt ever do this. They are wrong of course, so trying to find a workaround in the client at the moment. I'm not sure if this is the same bug or not, but I experienced something very similar. About 2/3 of the way through an extensive update (100's of MB), the downloads just stopped. I eventually exited the up2date gui via the 'cancel' button. While I didn't get a std error msg about the server being too busy, there was a python traceback left on the terminal, which included the text for such a msg: [root@slick grover]# up2date Traceback (most recent call last): File "/usr/share/rhn/up2date_client/gui.py", line 1448, in doRetrieval self.setRetrievalProgress) File "/usr/share/rhn/up2date_client/up2date.py", line 255, in getPackage buffer = rpcServer.doCall(rpmSource.psc.packageSource.getPackage, pkg, msgCallback, progressCallback) File "/usr/share/rhn/up2date_client/rpcServer.py", line 134, in doCall up2dateAuth.updateLoginInfo() File "/usr/share/rhn/up2date_client/up2dateAuth.py", line 110, in updateLoginInfo loginInfo = login() File "/usr/share/rhn/up2date_client/up2dateAuth.py", line 99, in login loginInfo = rpcServer.doCall(server.up2date.login, systemId) File "/usr/share/rhn/up2date_client/rpcServer.py", line 110, in doCall ret = apply(method, args, kwargs) File "/usr/lib/python2.2/xmlrpclib.py", line 821, in __call__ return self.__send(self.__name, args) File "/usr/lib/python2.2/site-packages/rhn/rpclib.py", line 123, in _request verbose=self._verbose File "/usr/lib/python2.2/site-packages/rhn/transports.py", line 133, in request return self.parse_response(fd) File "/usr/lib/python2.2/site-packages/rhn/transports.py", line 153, in parse_response return u.close() File "/usr/lib/python2.2/xmlrpclib.py", line 571, in close raise apply(Fault, (), self._stack[0]) xmlrpclib.Fault: <Fault -51: '\nError Message:\n Free service limited due to high load, please try again later (server 1001140430)\nError Class Code: 51\nError Class Info: \n Due to extremely high traffic, access to Red Hat Network is currently \n limited to subscription customers. Please try again later. If you \n would like to become a subscription customer, go to \n https://rhn.redhat.com/preview/priority_service.pxt for more information.\nExplanation: \n An error has occurred while processing your request. If this problem\n persists please submit a bug report to rhn-help.\n If you choose to submit the bug report, please be sure to include\n details of what you were trying to do when this error occurred and\n details on how to reproduce this problem.\n'> Grover: Yes I think it is the same bug. This _really_ leaves a bad taste in the mouth of a customer who paid for a boxed set. In case it might be of some use, I will attach my error messages. In my case, the up2date client process is hung. This leaves me wondering whether killing it will corrupt the RPM DB, etc. Maybe I should listen to the friend of mine who highly recommends Mandrake. :-( Created attachment 91762 [details]
error messages from up2date client dying
This is the stdout/stderr I got when up2date died, with
the client process hung.
Closing as 8.0 has expired, and the issue isn't relevant to FC1. |