On Nov 10, 7:33 pm, Maximiliano Guzenski
wrote:
> I already setted "ulimit -n 20" on linux, but it didn't fix this issue.
> I changed /etc/limits.conf as well.
You can double check the values being used by finding your app's
process id and then `cat /proc//limits`
--
Job Board: http://jobs.
looks like that "ulimit -n 20" does works:
cat /proc/3475/limits
Limit Soft Limit Hard Limit Units
Max cpu time unlimitedunlimitedseconds
Max file size unlimitedunlimitedb
I put on /etc/security/limits.conf (and restart):
ubuntu hardnofile 50
ubuntu softnofile 45
why did it not affect "cat /proc//limits" ?
On Sunday, November 11, 2012 9:11:12 AM UTC-2, Maximiliano Guzenski wrote:
>
> looks like that "ulimit
sorry: looks like that "ulimit -n 20" does NOT works...
On Sunday, November 11, 2012 9:14:50 AM UTC-2, Maximiliano Guzenski wrote:
>
> I put on /etc/security/limits.conf (and restart):
>
> ubuntu hardnofile 50
> ubuntu softnofile 45
>
> wh
On Nov 11, 6:16 am, Maximiliano Guzenski
wrote:
> sorry: looks like that "ulimit -n 20" does NOT works...
Try putting that in your upstart script right before you execute your
node script.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing
I was using "ulimit" into upstart script... that isn't work... becouse it
is just "limit", now is working!
description "xmpp node.js server"
author "Maximiliano Guzenski"
# used to be: start on startup
# until we found some mounts weren't ready yet while booting:
start on started mountall
s
I'm sorry to bump this, but it doesn't seem like this actually solves the
problem, it just allows files to accumulate longer. In general, my app
would have between 100 and 400 users connected to it. However, over time,
the number of open files increases at almost a linear rate. After running
fo
I have this issue as well - interestingly enough, also a webchat app, and
when I have ~400 online users, I get the EMFILE error. From looking around
at other issues with socket.io, it seems that this may be related
to https://github.com/LearnBoost/socket.io/issues/438 - in fact, I believe
the O
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 201
>
> Does anyone solved it in different way than change ulimit? Like The Yak
> wrote- it only allows files to accumulate longer so it is not solution.
>
>
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You receiv
10 matches
Mail list logo
