[zeromq-dev] Interrupted system call

MinRK benjaminrk at gmail.com
Thu Jul 28 13:58:13 CEST 2016


Following the behavior of Python 3.5, interrupted system calls are retried,
starting in pyzmq 14.7. 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.

-MinRK

On Thu, Jul 28, 2016 at 1:15 PM, Frédéric <fma at gbiloba.org> wrote:

> Le lundi 25 juillet 2016, Frédéric a écrit :
>
> > Mmm, this error only occurs on my RPi3; all work fine on my desktop
> > computer.
>
> Ok, zmq/pyzmq are not in the same versions on both machines:
>
> libzmq at desktop = 4.1.5
> pyzmq at desktop = 15.2.0
> python at rpi = 2.7.12
>
> libzmq at rpi = 4.0.5
> pyzmq at rpi = 14.4.0
> python at rpi = 2.7.9
>
> So, I installed pyzqm using pip, which gave me:
>
> libzmq at rpi = 4.1.5
> pyzmq at rpi = 15.3.0
>
> Now, I don't get the 'ZMQError: Interrupted system call' anymore when the
> log handler send the message from the process, but instead it blocks
> forever on this call :o/
>
> --
>     Frédéric
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20160728/f32fa67a/attachment.html>


More information about the zeromq-dev mailing list