To many open files...

[Ilan Berkner]

Thanks for the fast response.  Our site is back up :-).  Our tech support
(dedicated server support) did something to fix this issue, I will find out
later what.  I'll keep an eye on the open files as we currently have it set
pretty high.




On Tue, Jan 13, 2009 at 11:37 AM, Igor Sysoev <is at rambler-co.ru> wrote:

> On Tue, Jan 13, 2009 at 11:15:52AM -0500, Ilan Berkner wrote:
>
> > This morning, our server (www.spellingcity.com) went down and I can't
> figure
> > out why.  The Nginx log file has this error in it (all over the place and
> is
> > growing):
> >
> >
> > 2009/01/13 10:07:24 [alert] 26159#0: accept() failed (24: Too many open
> > files) while accepting new connection on 74.200.197.210:80<http://74.200.197.210/>
>
> This is OS limit that should be increased:
> http://www.google.com/search?q=linux+number+of+open+files
>
> > Which of course follows up with endless:
> >
> > 2009/01/13 10:14:56 [error] 26159#0: *13007 upstream timed out (110:
> > Connection timed out) while connecting to upstream, client: 131.109.51.3,
> > server: www.spellingcity.com, request: "GET / HTTP/1.0", upstream:
> > "fastcgi://127.0.0.1:9000", host: "www.spellingcity.com"
>
> This error may be associated with "Too many open files" as connecting
> to localhost should be done very quickly.
>
>
> --
> Igor Sysoev
> http://sysoev.ru/en/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20090113/f279ce0e/attachment.html>