What is the error in tcp-socket connections on nodejs?

Question

Node.js

Tell me, who knows. We make a game for contact. Nodejs has a tcp server that listens for connections from flash. everything works, the data goes back and forth. but after a couple of days, flash can't connect with nodejs. At the same time, the nodejs process does not fall off, it does not give any errors. I checked the memory leak using memwatch, everything seems to be fine too. The onError handler is on the tcp server and on the socket, they also do not catch errors. Maybe someone faced the problem?
Just in case, here is the code: pastebin.ru/fX4db5b7

Answer 1

The question went like this: in the function that logged errors and service information, I forgot to close the open file descriptor. and in linux there is a limit on the number of open handles, so after a certain number of connections, the handle limit was reached and a new connection could not be opened7

Answer 2

I came across, in my case, such a misfortune happened when, due to an application crash, it was restarted through forever, and for some reason, after such a restart, just such a situation arose. treated by updating node.js and the forever package. now on node v0.10.28, I didn’t see anything like this