Just wanted to add a +1 to this issue. I had the same difficulties when moving my project to a new PC. I'd installed the latest version of Node and was coming across these errors with no idea as to why. I found this post, uninstalled Node and reinstalled an older version, then found my ECONNRESET issue had disappeared.
On Tuesday, May 21, 2013 7:19:12 PM UTC+10, Ben Noordhuis wrote: > > On Tue, May 21, 2013 at 3:58 AM, Stuart > <[email protected]<javascript:>> > wrote: > > 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? > > The ECONNRESET is what is reported by the operating system so > evidently it thinks the connection has been reset. > > If, for example, the peer sends a FIN before the connection has been > fully established (SYN sent but no ACK received yet), then most > operating systems will consider that a reset. ECONNABORTED would have > made more sense IMO but it is what it is. > -- -- 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.
