Databases
StackOverflow2013
Postsdbo
PONode js ECONNRESET
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONode js ECONNRESET
    primarykey
    data
    text
    <p>I m running an Express js application with socket.io for a chat webapp and I get the following error randomly around 5 times during 24h. The node process is wrapped in forever and it restarts itself immediately.</p> <p>Problem is that restarting express kicks my users out of their rooms and nobody wants that.</p> <p>The web server is proxied by HAProxy. There are no socket stability issues, just using websockets and flashsockets transports. I cannot reproduce this on purpose. </p> <p>This is the error with node v0.10.11: </p> <pre><code>events.js:72 throw er; // Unhandled 'error' event ^ Error: read ECONNRESET //alternatively it s a 'write' at errnoException (net.js:900:11) at TCP.onread (net.js:555:19) error: Forever detected script exited with code: 8 error: Forever restarting script for 2 time </code></pre> <p><strong>EDIT (2013-07-22)</strong></p> <p>Added both socket.io client error handler and the uncaught exception handler. Seems that this one catches the error:</p> <pre><code>process.on('uncaughtException', function (err) { console.error(err.stack); console.log("Node NOT Exiting..."); }); </code></pre> <p>So I suspect it's not a socket.io issue but an http request to another server that I do or a mysql/redis connection. Problem is that the error stack doesn't help me identify my code issue. Here is the log output: </p> <pre><code>Error: read ECONNRESET at errnoException (net.js:900:11) at TCP.onread (net.js:555:19) </code></pre> <p>How do I know what causes this? How do I get more out of the error? </p> <p>Ok, not very verbose but here s the stacktrace with "longjohn":</p> <pre><code>Exception caught: Error ECONNRESET { [Error: read ECONNRESET] code: 'ECONNRESET', errno: 'ECONNRESET', syscall: 'read', __cached_trace__: [ { receiver: [Object], fun: [Function: errnoException], pos: 22930 }, { receiver: [Object], fun: [Function: onread], pos: 14545 }, {}, { receiver: [Object], fun: [Function: fireErrorCallbacks], pos: 11672 }, { receiver: [Object], fun: [Function], pos: 12329 }, { receiver: [Object], fun: [Function: onread], pos: 14536 } ], __previous__: { [Error] id: 1061835, location: 'fireErrorCallbacks (net.js:439)', __location__: 'process.nextTick', __previous__: null, __trace_count__: 1, __cached_trace__: [ [Object], [Object], [Object] ] } } </code></pre> <p>Here I serve the flash socket policy file:</p> <pre><code>net = require("net") net.createServer( (socket) =&gt; socket.write("&lt;?xml version=\"1.0\"?&gt;\n") socket.write("&lt;!DOCTYPE cross-domain-policy SYSTEM \"http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd\"&gt;\n") socket.write("&lt;cross-domain-policy&gt;\n") socket.write("&lt;allow-access-from domain=\"*\" to-ports=\"*\"/&gt;\n") socket.write("&lt;/cross-domain-policy&gt;\n") socket.end() ).listen(843) </code></pre> <p>Can this be the cause? </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCarl Manaster
    1. USSamson
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PONode js ECONNRESET
      1. USSamson
      1. VTFavorite
    2. VO
      singulars
      1. PONode js ECONNRESET
      1. USGottZ
      1. VTFavorite
    3. VO
      singulars
      1. PONode js ECONNRESET
      1. USMiguel
      1. VTFavorite
    1. CO@GottZ maybe this can help (spoke to someone working within node js) https://gist.github.com/samsonradu/1b0c6feb438f5a53e30e. I ll deploy the socket.error handler today and let you know.
      singulars
      1. PONode js ECONNRESET
      1. USSamson
    2. CO@Gottz the socket.error handles doesn t help, but process.on('uncaughtException') catches the error. Here is the console.log of the error: { [Error: read ECONNRESET] code: 'ECONNRESET', errno: 'ECONNRESET', syscall: 'read' }
      singulars
      1. PONode js ECONNRESET
      1. USSamson
    3. COECONNRESET could be from network problem. As you know it is impossible to catch all the exceptions when testing. Some will show up on your production server. You will have to make your server robust. You can handle the session deletion by using Redis as storage. It makes your sessions persist even after your node server goes down.
      singulars
      1. PONode js ECONNRESET
      1. USuser568109
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload