[zeromq-dev] Interrupted system call

Frédéric fma at gbiloba.org
Thu Jul 28 14:28:45 CEST 2016

Le jeudi 28 juillet 2016, MinRK a écrit :

> Following the behavior of Python 3.5, interrupted system calls are
> retried, starting in pyzmq 14.7.

I tried added a manual retry, but this does not help.

> Are you creating the sockets after forking with multiprocessing? You
> shouldn't use any sockets that were created in the host process in any
> of the forks.

Mmm, no, I don't instanciate a new socket :o/

I have to figure out how to do that with my Singleton logger and
multiprocessing module...

This is strange that it work fine a simple example, or even in my complete
application on my desktop PC, and fail on Rpi... What can cause such
behaviour difference?

BTW, could someone resume what is needed to re-create or not in a
multi-threaded and multi-processing context? Is ok to share Context? When
do I need to use zmq.Context() or zmq.Context.instance() ?



More information about the zeromq-dev mailing list