Thanks a lot for the link. Unfortunately it didn't help. @roberto: the uwsgi process is then indeed eating all the CPU - but I'm not sure it means uwsgi is the culprit, at least at this stage (could be the case earlier though). Is there in linux a way to know who opened which file and when? lsof gives only the process, not the time.
Le mercredi 24 juillet 2013 23:56:10 UTC+2, Niphlod a écrit : > > it's a problem on the layers "at the base" of web2py, such as the os, > nginx or uwsgi. > http://www.cyberciti.biz/faq/linux-unix-nginx-too-many-open-files/ > let's see if @roberto (the developer behind uwsgi) passes by with some > useful tips too. > > On Wednesday, July 24, 2013 4:30:51 PM UTC+2, dederocks wrote: >> >> I'm running web2py on nginx /uwsgi. >> And in a sequence implying frequent serveur calls, I eventually get an >> error 500 from the server, which is actualy an error 24: too many files >> open (see ticket in attachement). >> >> I checked former reports on this error, but none seems to match this >> case: I'm not using rocket, and running the latest web2py stable version. >> I checked also on opening files myself, but that is never the case (e.g. >> always done by web2py). >> I tried to increase the file opened limit (ulimit -SHn 4048), but to no >> improvement. >> >> Any suggestion? >> >> Thanks in advance, Andre >> >> >> -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
