[Mailman-Users] Stuck OutgoingRunner

Sebastian Hagedorn Hagedorn at uni-koeln.de
Tue Feb 6 06:51:50 EST 2018

--On 4. Februar 2018 um 12:54:43 +0900 Yasuhito FUTATSUKI 
<futatuki at poem.co.jp> wrote:

> On 02/04/18 12:13, Mark Sapiro wrote:
>> The status of 'S' for OutgoingRunner is "uninterruptable sleep". This
>> means it's either called time.sleep for QRUNNER_SLEEP_TIME (default = 1
>> second) which is unlikely as it should wake up, or it's waiting for
>> response from something, most likely a response from the MTA.
> As far as I read the code, if OutgoingRunner catch SIGINT during waiting
> for response from the MTA, the signal handler for SIGINT in qrunner set
> flag to exit from loop, then socket module raise socket.error for EINTR,
> but SMTP module retry to read from socket and waiting for response until
> receiving response or connection closing (from MTA side or by error).
> Thus it cannot reach to the code to exit if the connection is kept alive
> and MTA send no data.

Thanks. I think that might be a possible explanation, but what could cause 
a SIGINT to be sent to the OutgoingRunner?
    .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:.
                 .:.Regionales Rechenzentrum (RRZK).:.
   .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.

More information about the Mailman-Users mailing list