when this error come how to solve this error

Question

I am developing an app in node.js socke.io redis mysql , so this error arrvied some time don't know when it arrived and how to find where this error come , how to solve this error .?

node.js:178
        throw e; // process.nextTick error, or 'error' event on first tick
        ^
Error: ETIMEDOUT, Connection timed out
    at Socket._onConnect (net.js:600:18)
    at IOWatcher.onWritable [as callback] (net.js:186:12)**strong text**

Answer 1

I believe I read somewhere on stackoverflow or someplace that socket.io is not yet completely comptatible with 0.5.0-pre. Could you try the latest official build v0.4.8 instead and report back?

---

That's correct :). I read it on stackoverflow.com and found the link to it also: node v0.5.0 pre Socket.IO crashes on connection (independent of transport)

Answer 2

This is caused by a socket error emitting an "error" event, but not finding any listeners for "error" events. In this case, node converts the event into an exception.

So the simple thing to check is make sure that you are listening for errors on all of your connections.

There is a tricky bug right now where some sockets emit errors before, or possibly after the user code can be listening for errors. I see this a lot when doing HTTPS. If you are hitting this uncatchable error situation, there's not much you can do about this besides changing node to not convert those socket errors into exceptions. If you can come up with a reliable way to reproduce this issue, it'll get fixed much more quickly.