I too have been seeing ECONNRESET. In my case, the ECONNRESET comes from a server that sends no data to the socket, does nothing but send a FIN packet. As I understand TCP, while this isn't ordinary, it isn't illegal, nor is it a reset. Since the server didn't send a RST packet, but a FIN, shouldn't the socket close report an end event?
On Friday, April 5, 2013 12:19:21 PM UTC-4, Jochen Delabie wrote: > > Since we updated from Node 0.8 to Node 0.10 we're seeing these errors: > > { [Error: read ECONNRESET] code: 'ECONNRESET', errno: 'ECONNRESET', > syscall: 'read' } > Error: read ECONNRESET > at errnoException (net.js:878:11) > at TCP.onread (net.js:539:19) > > > I know this error was previously ignored before 0.10, but I'd like to know > what's causing this and how I can fix it/debug it? > Is it a problem on our end (server) closing connections too soon? > > Thanks! > -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com 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 nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.