You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My http service (using both http and socket.io) had crash after run for long time. I don't know how to make this error again. Please help to know what error and any solution for it. I will deploy to Linux production server any problem with it?
The short answer though is the remote party terminated the connection abruptly while node was reading from the socket. Somewhere in your code or the code of a dependency module, an 'error' event handler is not being added (probably to the socket object), causing the exception to be thrown.
For reference, there's quite a few people coming up against similar uncatchable errors in libraries like request and socket.io - they're not even catchable with process.on('uncaughtException', ...). Some clues here: request/request#2161
My http service (using both http and socket.io) had crash after run for long time. I don't know how to make this error again. Please help to know what error and any solution for it. I will deploy to Linux production server any problem with it?
events.js:160
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at exports._errnoException (util.js:1022:11)
at TCP.onread (net.js:569:26)
The text was updated successfully, but these errors were encountered: