> Unfortunately the issue persists, albeit at a lesser scale. Spooler > jobs were successfully created this morning and the workers don't > appear to be dying off quite as often. The config is the same as I > had posted before minus the max-requests and optimize flags. Here are > two excerpts from the logs: > >
Ok, this confirm an issue with max-requests and the spooler (propagating to workers). Your latest errors seems triggered by the signal handling subsystem. I do not know if you need to spawn threads in your app, but if you do not need it, please disable --enable-threads to see if the signal-handler crash is triggered by a broken GIL lock. Many Thanks -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
