[zeromq-dev] broken pipe on remote shutdown
bklooste at gmail.com
Thu Sep 20 01:46:45 CEST 2012
Doesnt the kernel send an EPIPE if you do a read on a socket where the
other end has sent a TCP RST , lots of routers send this so you need to
On Thu, Sep 20, 2012 at 12:22 AM, Yi Ding <yi.s.ding at gmail.com> wrote:
> On Wed, Sep 19, 2012 at 10:49 AM, Chuck Remes <lists at chuckremes.com>
> > 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.
> > cr
> 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.
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the zeromq-dev