> Hi, > > I have big problem with uWSGI. From time to time (in rush hours) uWSGI > just hangs and throws such messages: > > Wed Sep 14 19:01:51 2011 - *** uWSGI listen queue of socket 3 full !!! > (129/128) *** > Wed Sep 14 19:01:52 2011 - *** uWSGI listen queue of socket 3 full !!! > (128/128) *** > Wed Sep 14 19:01:55 2011 - *** uWSGI listen queue of socket 3 full !!! > (129/128) *** > Wed Sep 14 19:01:56 2011 - *** uWSGI listen queue of socket 3 full !!! > (129/128) *** > timeout. skip request. >
This is a warn for your configuration not being able to manage the current rate of requests. Your 48 processes scares me a bit, on high-load you will ends with 48 postgresql and 48 uwsgi processes probably devouring your ram/cpu. (try to launch a top when this happens, to see the machine status) I suggest you decreasing them (there is no one-fit-for-all value). Probably when you see this your server is pratically unusable. Remember that you could avoid postgresql-connection-storming using something like pgpool. After decreasing processes you will probably need to increase the listen queue. Remember that on Linux you have to increase the max limit (128 by defaut) using sysctl. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
