This error is fixed here: http://stackoverflow.com/questions/16476783/node-js-ssl-server-frozen-high-cpu-not-crashed-but-no-connections
It's related with the limit of files a process is able to open in linux. I wrote it my self so if you need any help please tell me. On Sunday, 11 November 2012 01:33:28 UTC+1, Maximiliano Guzenski wrote: > > Hi, > I have a webchat, running with socket.io (no redis) and express into a > EC2 m1.small. > When I have 420 online users, nodejs/socket.io go in an error looping... > in log I can see: > > warn: error raised: Error: accept EMFILE > warn: error raised: Error: accept EMFILE > warn: error raised: Error: accept EMFILE > warn: error raised: Error: accept EMFILE > ... many times ... > > ubuntu upstart doesn't detect this error, and my app be in an error loop > forever. > > I already setted "ulimit -n 200000" on linux, but it didn't fix this > issue. I changed /etc/limits.conf as well. > > I use nodejs 0.8.14 and last version of socket.io > > My app use less then 30% of memory and 10% of CPU. > > Please, anyone can helpe me? > > -- -- 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.
