> We're running uwsgi 0.9.8.3 on Ubuntu 10.04LTS.  We're using syslog for
> the logs, and it's working great (in the past we had issues, but Roberto
> fixed them super quick - thanks Roberto!).
>
> Anyway, everything looks fine - EXCEPT for exceptions.  Before, when we
> were logging directly to a logfile, we'd see occasional exceptions like
> this:
>
> Exception _mysql_exceptions.ProgrammingError: (2014, "Commands out of
> sync; you can't run this command now") in <bound method Cursor.__del__ of
> <MySQLdb.cursors.Cursor object at 0x75df9d0>> ignored
>
> Now we're seeing them look like this:
>
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: Exception
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: _mysql_exceptions
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: .
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: ProgrammingError
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: :
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: (
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: 2014
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: ,
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: "
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: C
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: o
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: m
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: m
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: a
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: n
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: d
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: s
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi:
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: o
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: u
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: t
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi:
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: o
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: f
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi:
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: s
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: y
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: n
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: c
> Oct 10 12:57:21 prod-api-www2 djcore-uwsgi: ;
>
> ... etc.
>
> Is there some setting that I'm missing to handle this a little more
> gracefully?
>
>


Try the latest tip (or pull from github)

You can emulate the same behaviour adding

import sys; sys.stdout = sys.stderr

on the very top of your app

Otherwise (as a workaround) check sys.excepthook

map it to a function that print the exception in one line and print it,
otherwise send it directly to syslog as a packet.

Let me know if it works for you

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

Reply via email to