Lots of 2009/09/27 00:49:21 [alert] 22383#0: accept() failed (24: Too many open files)
Jason Kim
highclass99 at gmail.com
Sun Sep 27 05:42:29 MSD 2009
I am running CentOS 5.3, from what I know default limits for standard users
file is 200000
Anyways to make sure I edited /etc/passwd to
apache:x:48:48:Apache:/var/www:/bin/bash
So I could login as apache (I set niginx.conf as user apache apache;)
and then as root typed
[root at firewall2 ~]# su apache
and then as apache typed
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 77824
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 200000
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 77824
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Is there any reason I still should bump into file limits?
Thanks
On Sun, Sep 27, 2009 at 7:53 AM, Payam Chychi <pchychi at gmail.com> wrote:
> how is this related to his question? hoe does ur answer help him in
> figuring out the issiue?
>
> Jason, check ur ulimits for the user running the process, alsomale sure to
> update /etc/security/limits so new changed take place at boot
>
> Regards,
> --
> Payam Tarverdyan Chychi
> Network Engineer
>
> Sent from my iPhone
>
>
> On 2009-09-26, at 11:02 AM, Dennis Brakhane <brakhane at googlemail.com>
> wrote:
>
> On Sat, Sep 26, 2009 at 5:59 PM, Jason Kim <highclass99 at gmail.com> wrote:
>>
>>> worker_processes 12;
>>>
>>
>> Do you really have 12 cores? It doesn't make much sense to have more
>> workers than cores
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20090927/fd3ed425/attachment.html>
More information about the nginx
mailing list