As a follow up, if anyone else sees this, this post was helpful and appears related, all streams need the on error listener
https://groups.google.com/forum/?fromgroups=#!searchin/nodejs/EPIPE/nodejs/lJYT9hZxFu0/brImF1aRFlMJ On Thursday, March 21, 2013 8:36:51 PM UTC-7, Rich Schiavi wrote: > > Anyone have any idea why *with* an .on('error') handler on a socket, the > EPIPE exception is still being thrown as an uncaught. (And on the domain). > If you see this log below, you see where my socket.on('error') handler > prints the error (so it catches it, it's attached and working ;-)) but so > does process.on('uncaught) and domain.on('error) > > > 2013-03-22T03:20:49.233Z - warn: socket.on('error') socket error: Error: > write EPIPE > 2013-03-22T03:20:49.245Z - error: PROCESS ON UNCAUGHT EXCEPTION: Error: > write EPIPE > 2013-03-22T03:20:49.245Z - error: stack: Error: write EPIPE > at errnoException (net.js:770:11) > at Object.afterWrite (net.js:594:19) > 2013-03-22T03:20:49.246Z - error: domain error: Error: write EPIPE : > Error: write EPIPE > at errnoException (net.js:770:11) > at Object.afterWrite (net.js:594:19) > > This is node 0.8.18 on Linux > > > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
