Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 88270 - Exception not being handled for SSL.SysCallError
Summary: Exception not being handled for SSL.SysCallError
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rhn-applet
Version: 9
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Robin Norwood
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-08 14:34 UTC by Arenas Belon, Carlo Marcelo
Modified: 2007-04-18 16:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-10-17 19:49:27 UTC

Attachments (Terms of Use)

Description Arenas Belon, Carlo Marcelo 2003-04-08 14:34:30 UTC
Description of problem:
an Exception of type SSL.SysCallError was received on the applet and reported as
a bug with a question mark icon

Version-Release number of selected component (if applicable):

How reproducible:
probably related to some maintenance on the RHN servers, i could try to block
the RHN servers and see if i can reproduce the error, but my guess is that i
could reproduce it re routing the RHN servers to a server not listening or
rejecting XMLRPC over HTTPS connections

Actual results:
Exception type SSL.SysCallError

Exception Handler Information
Traceback (most recent call last):
  File "/usr/bin/../share/rhn/rhn_applet/", line 448, in refresh
  File "/usr/bin/../share/rhn/rhn_applet/", line 264, in refresh
  File "/usr/bin/../share/rhn/rhn_applet/", line 84, in refresh
    status = server.applet.poll_status()
  File "/usr/lib/python2.2/", line 821, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python2.2/site-packages/rhn/", line 126, in _request
  File "/usr/lib/python2.2/site-packages/rhn/", line 130, in request
    headers, fd = req.send_http(host, handler)
  File "/usr/lib/python2.2/site-packages/rhn/", line 614, in send_http
  File "/usr/lib/python2.2/", line 701, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib/python2.2/", line 723, in _send_request
  File "/usr/lib/python2.2/", line 695, in endheaders
  File "/usr/lib/python2.2/", line 581, in _send_output
  File "/usr/lib/python2.2/", line 560, in send
  File "/usr/lib/python2.2/site-packages/rhn/", line 191, in write
    sent = self._connection.send(data)
SysCallError: (104, 'Connection reset by peer')

Expected results:
the usual "ok" icon

Additional info:
the problem was gone once i "reconfigure" the rhn-applet

Comment 1 Arenas Belon, Carlo Marcelo 2003-04-08 15:17:33 UTC
interesting also that just after the problem i got a report that my kernel was
not up2date as reported on bug #84757.

both problems disapeered once i right click on the applet and went thru the
"configure" process again

couldn't add this same comment to ticket #84757 tough as the ticket broken as
explained on bug #87920

Comment 2 Daniel Veillard 2003-04-08 16:41:04 UTC
Well it's an error connecting to the server, I doubt it's a registration
based problem. Are you using a free RHN slot or a paid one ? Anyway
I tried to make sure the exception will be properly caught in future
version of the rhn-applet package.


Comment 3 Arenas Belon, Carlo Marcelo 2003-04-08 17:01:36 UTC
i am using a paid RHN slot (uuid=6931413a-6673-11d7-80a0-00d059543bd1).

after giving it some more thought, i think the problem should maybe better be
handled on the package for rhnlib 1.0 where there is no exception
handling an SSL.SysCallError on the write method as it is currently being
handled on the read method, otherwise the SSL subsystem wouldn't give consistent

the problem couldn't be replicated just trying to fool rhnsd or blocking access
to the RHN server as the problem was presented while writing to the established
and authenticated SSL connection

Comment 4 Warren Togami 2003-04-11 22:20:46 UTC
This same error happened to me on Shrike.  I am a paid RHN customer.

Comment 5 Daniel Veillard 2003-04-11 22:29:42 UTC
The applet (nor the SSL layer) do not catch up all the connection errors,
however it tries to recover from them. Did the icon turned grey with an
interrogation mark (i.e. it got stuck in the error state) or did it indicated
a connection error (double arrow on grey background crossed with a red strike) ?
In the last case it will retry the connection automatically until it succeeds
and the error message is then purely informative.


Comment 6 Arenas Belon, Carlo Marcelo 2003-04-12 00:06:15 UTC
as i reported initially i got an interrogation mark (AKA question mark), a gray
one indeed.

Comment 7 Bill Nottingham 2006-08-05 04:23:02 UTC
Red Hat apologizes that these issues have not been resolved yet. We do want to
make sure that no important bugs slip through the cracks.

Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc.
They are maintained by the Fedora Legacy project (
for security updates only. If this is a security issue, please reassign to the
'Fedora Legacy' product in bugzilla. Please note that Legacy security update
support for these products will stop on December 31st, 2006.

If this is not a security issue, please check if this issue is still present
in a current Fedora Core release. If so, please change the product and version
to match, and check the box indicating that the requested information has been

If you are currently still running Red Hat Linux 7.3 or 9, please note that
Fedora Legacy security update support for these products will stop on December
31st, 2006. You are strongly advised to upgrade to a current Fedora Core release
or Red Hat Enterprise Linux or comparable. Some information on which option may
be right for you is available at

Any bug still open against Red Hat Linux 7.3 or 9 at the end of 2006 will be
closed 'CANTFIX'. Again, if this bug still exists in a current release, or is a
security issue, please change the product as necessary. We thank you for your
help, and apologize again that we haven't handled these issues to this point.

Note You need to log in before you can comment on or make changes to this bug.