On Tue, Oct 23, 2012 at 8:03 PM, Roberto De Ioris <[email protected]> wrote:
> This is from the python logging module, not from uWSGI
Well, the error traceback is printed from there, but that's just a
write to stdout. The error (or at least *an* error) happens also if I
try using uwsgi.log (as my closest path to a direct native write to
the file descriptor)
import uwsgi
irange = range(1030, 1042)
for i in irange + list(reversed(irange)):
uwsgi.log('%8d %s' % (i, 'X' * i))
uwsgi.log("Does this make it out?")
(I halved the byte count because I got almost no messages otherwise;
don't know why that is. Is uwsgi.log sending UTF-16 maybe?)
>From this I get a small and random subset of the 24 expected long
messages, but always the final message:
1030 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...
1031 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...
1032 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...
1033 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...
Does this make it out?
Presumably the missing writes are failing with those same errors 40
and 55; uwsgi_log just doesn't check for an error.
So whatever causes this, it's not python's logging. :)
Gulli
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
