Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mirrorprobe sometimes times out with an exception #46

poeml opened this issue Jun 5, 2015 · 0 comments

mirrorprobe sometimes times out with an exception #46

poeml opened this issue Jun 5, 2015 · 0 comments


Copy link

@poeml poeml commented Jun 5, 2015

                                                                                                    [          ]

Issue migrated (2015-06-05) from old issue tracker

Title    mirrorprobe sometimes times out with an exception
 Priority   bug               Status        resolved
Superseder                  Nosy List       poeml
Assigned To poeml            Keywords

msg165 (view) Author: poeml Date: 2010-03-27.15:10:53

There is a certain exception that the mirrorprobe might run into, which is not caught by the code,
even though it should. Symptom:

Exception in thread probeThread-273:
Traceback (most recent call last):
File "/usr/lib/python2.5/", line 486, in __bootstrap_inner
File "/usr/lib/python2.5/", line 446, in run
self.__target(_self.__args, *_self.__kwargs)
File "/usr/bin/mirrorprobe", line 97, in probe_http
mirror.response =
File "/usr/lib/python2.5/", line 291, in read
data = self._sock.recv(recv_size)
File "/usr/lib/python2.5/", line 509, in read
return self._read_chunked(amt)
File "/usr/lib/python2.5/", line 544, in _read_chunked
line = self.fp.readline()
File "/usr/lib/python2.5/", line 331, in readline
data = recv(1)
timeout: timed out

The code does have exception handling for this case. However, the exception, which happens deep
in the socket module, is not correctly passed to upper layers. Thus, there doesn't seem to be a way
to get hold of it.

In trunk, I have now wrapped the entire thread code into another try-except block. That is ugtly,
but helps.

msg166 (view) Author: poeml Date: 2010-03-27.15:20:57

r8022 | poeml | 2010-03-27 16:19:13 +0100 (Sat, 27 Mar 2010) | 8 lines


  • A hard-to-catch exception is now handled. If Python's socket module ran into
    a timeout while reading a chunked response, the exception would not be passed
    correctly to the upper layer, so it could not be caught by its name. We now
    wrap the entire thread into another exception, which would otherwise be bad
    practice, but is probably okay here, since we already catch all other exceptions.
         Date         User  Action            Args
2010-03-27 15:20:57 poeml set    status: testing -> resolved
                                   messages: + msg166
2010-03-27 15:10:54 poeml create

(end of migrated issue)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant