> throttle_level looks to be set to 2. Can't see any OOMs in the dmesg > logs, no... >
hi, i mean during the "cascade problem", if that value is high it could explain the problem. By the way, have you tried latest code ? > > -- > Harry Percival > Developer > [email protected] > > PythonAnywhere - a fully browser-based Python development and hosting > environment > <http://www.pythonanywhere.com/> > > PythonAnywhere LLP > 17a Clerkenwell Road, London EC1M 5RD, UK > VAT No.: GB 893 5643 79 > Registered in England and Wales as company number OC378414. > Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK > > On 10/03/14 16:22, Roberto De Ioris wrote: >>> Can you think of any reason why the cascade is happening? why all new >>> vassals are affected? >> The only thing popping-up in my mind is that for some reason you have a >> very-high throttle level (it is the throttle_level attribute in the >> emperor stats). >> >> So you are effectively blocked from spawning new processes (for a pretty >> long time) >> >> During the "problem" you see the vassal list in the stats server, so the >> case of a corruption in the linked list is not a possibility. >> >> Can you check if there is some OOM in the dmesg ? >> > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
