Skip to content

Unhandled EPIPE error #15

Closed
mbrevoort opened this Issue Oct 22, 2012 · 1 comment

1 participant

@mbrevoort

My Seaport server regularly bombs with EPIPE exceptions especially in AWS. I assume these are broken dnode connection interruptions on the socket, right? it would be great if Seaport would recover from these and the layer handling the socket would bind on("error").

Error: write EPIPE
    at errnoException (net.js:670:11)
    at Object.afterWrite [as oncomplete] (net.js:503:19)

Am I right to assume it's at the dnode layer this should be handled?

@mbrevoort

should be fixed in #28

@mbrevoort mbrevoort closed this Apr 5, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.