1024 Connection Limit
Alex Davies
alex at davz.net
Mon Aug 16 16:14:44 BST 2010
Hi All,
To answer my own question, the answer is to add this to the upstart file:
limit nofile 80000 80000
#limit nofile unlimited unlimited
I found that unlimited failed to work, so I just set a limit similar
to that of uname -n on my system.
It does seem the upstart default is 1024, regardless of ulimit. I am
not sure if this is a feature or a bug, but it caused me some
problems!
Many thanks,
Alex
On Fri, Aug 13, 2010 at 12:25 AM, Alex Davies <alex at davz.net> wrote:
> Hi,
> I apologise if this is not the correct mailing list to ask this question.
> As a inexperienced user of upstart, I have several times hit what appears to
> be a limit of 1024 connections for jobs started by upstart. For example, the
> following super-simple upstart job:
> start on runlevel [3456]
> stop on runlevel [!3456]
> script
> /opt/mongod/mongod --config=/etc/mongo/mongod.conf
> end script
> Will start a MongoDB process which will believe that the output of ulimit -n
> is 1024. Starting it on the command line will produce the correct value (in
> my case, an order of magnitude more).
> I cant find this obvious in the documentation; is there a easy way to remove
> this limit?
> Many thanks!
>
> Alex
--
Alex Davies
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail and delete this e-mail permanently.
More information about the upstart-devel
mailing list