[zeromq-dev] broken pipe on remote shutdown
yi.s.ding at gmail.com
Wed Sep 19 18:22:42 CEST 2012
On Wed, Sep 19, 2012 at 10:49 AM, Chuck Remes <lists at chuckremes.com> wrote:
> On Sep 19, 2012, at 9:56 AM, Yi Ding wrote:
>> This is on linux with ZMQ 2.2.0
>> On Wed, Sep 19, 2012 at 9:49 AM, Yi Ding <yi.s.ding at gmail.com> wrote:
>>> Hi everyone,
>>> I got a strange error today where one of my servers threw an assertion
>>> when I killed a remote.
>>> Here's the error:
>>> Broken pipe (.../external/zmq/src/tcp_socket.cpp:229)
>>> Looking at it, it looks like it's just a recv call, but I'm not sure
>>> why it would send back a EPIPE.
> Unfortunately, without a code snippet to reproduce the problem this kind of report is useless. If you can figure out a way to reliably reproduce this issue then we can try and fix it.
It's the first time I've seen it myself. I'll try to see if there's a
way to reproduce it, but was wondering more generally why we'd get a
EPIPE on a TCP socket.
More information about the zeromq-dev