After a little more research, it looks like the php-cgi processes that are being proxied to by nginx may be the problem. It looks like the php-cgi processes had a lot of files left open.<br><br>I ran `lsof | wc -l` and the result was 139566<br>
<br>After a restart of the php-cgi processes, the result was only 12045<br><br><div class="gmail_quote">On Wed, Apr 30, 2008 at 10:46 PM, Davy Campano <<a href="mailto:dcampano@gmail.com">dcampano@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">Davy Campano <dcampano@...> writes:<br>
<br>
><br>
> I'm getting a "Too many open files in system" error after running for about 10<br>
minutes. I'm in the process of testing out nginx and it's a pretty busy server<br>
doing around 200 requests/sec. My current open file limit is 131072. Does<br>
anyone know a safe amount to set this to for a 32-bit linux system with 6GB ram?<br>
<br>
</div></div>ulimit -n actually returns 1024, i'm thinking this should be higher<br>
<br>
cat /proc/sys/fs/file-max returns 131072<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div><br>