Hello Roberto, thank you for the -ignore tips
about first one, I think they are related to wrong request format - maybe some bots or flooders not sure what is this. but it's for sure not related to caching system, as we are moved to memcache and cache in uwsgi is disabled. so any idea, how to ignore them?) Sunday, September 9, 2012, 4:18:22 PM, you wrote: >> we have tons of traffic, and many of these messages are useless, but >> they are filling our logs very fast. >> >> recvmsg(): Resource temporarily unavailable [proto/uwsgi.c line 40] >> Sun Sep 2 14:46:50 2012 - error parsing request >> recvmsg(): Resource temporarily unavailable [proto/uwsgi.c line 40] >> Sun Sep 2 14:46:50 2012 - error parsing request > if they are related to caching subsystem, just upgrade to 1.2.6 (or 1.3 tree) >> >> Sun Sep 2 14:48:13 2012 - write(): Broken pipe [proto/uwsgi.c line 143] >> during GET >> > they are related to disconnecting clients and can be controlled via > --ignore-write-errors > and > --ignore-sigpipe -- Best regards, Test157 mailto:[email protected] _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
