Il giorno 11/set/2012, alle ore 21:07, Ævar Arnfjörð Bjarmason 
<[email protected]> ha scritto:

> On Sun, Sep 9, 2012 at 5:18 PM, Roberto De Ioris <[email protected]> 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
> 
> On a related note since throwing lots of traffic at uWSGI my error
> logs are mostly these messages:
> 
>    $ git --no-pager grep -i -e 'psgix.harakiri.commit requested' \
>      -e 'The work of process.*seeya' \
>      -e 'Respawned uWSGI worker' \
>      -e 'spawned uwsgi worker %d'
>    core/master_utils.c:525:
> uwsgi_log("Respawned uWSGI worker %d (new pid: %d)\n", wid, (int)
> pid);
>    core/master_utils.c:528:                        uwsgi_log("spawned
> uWSGI worker %d (pid: %d, cores: %d)\n", wid, pid, uwsgi.cores);
>    core/uwsgi.c:770:       uwsgi_log("...The work of process %d is
> done. Seeya!\n", getpid());
>    plugins/gevent/gevent.c:74:     uwsgi_log("...The work of process
> %d is done. Seeya!\n", getpid());
>    plugins/psgi/psgi_plugin.c:524:         uwsgi_log("***
> psgix.harakiri.commit requested ***\n");
> 
> Is there a switch for those I haven't spotted?
> 

I think the whole uWSGI project has a 'mantra' of "do not spend too much time 
searching for the right behaviour, as making all happy
is impossibile". For such a reason i have added (in 1.3 tip) a new option:

--log-drain <regexp>

if a logline matches the regexp, the log line will be "drained" (not 
showed/processed)

The regexp matching is done by the master, so it should have zero-impact on 
your app.

PAY ATTENTION: --log-drain works in every single line spitted out by uWSGI 
(request logs included)

--
Roberto De Ioris
http://unbit.it
JID: [email protected]

_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to