> Hi,
>
> I’ve been working with a Flask app (on Python 3.3) recently, and don’t
> seem to be getting any tracebacks in uwsgi’s log file. The application
> works just fine, but when an exception is generated, I get something like
> this with no traceback at all:
>
> [pid: 1251|app: 0|req: 1/1] 127.0.0.1 () {42 vars in 692 bytes} [Fri Jan
> 24 16:54:28 2014] POST /posts/ => generated 10280 bytes in 14 msecs
> (HTTP/1.0 500) 2 headers in 99 bytes (1 switches on core 0)
>
> Here’s a sample config file(that has had a few things, like the appname
> redacted):
>
> [uwsgi]
>
> virtualenv = /var/virtualenvs/appname/
>
> gid = uwsgi
> uid = uwsgi
> pidfile = /tmp/appname-master.pid
>
> # Log related configuration
> logfile-chmod = 664
> log-backupname = /var/log/uwsgi/appname-old.log
>
> harakiri-verbose = False
> logto = /var/log/uwsgi/appname.log
> log-maxsize = 10485760
>
> # Python / uWSGI Environment
> chdir = /var/app_path/appname/
> master = True
> module = appname:app
>
> max-requests = 5000
> buffer-size = 32768
> post-buffering = 4096
>
> http-socket = localhost:8000
>
> plugin = python33
>
> processes = 4
> stats = :1717
> enable-threads = True
>
>
> Hopefully I’m just missing something obvious here, because my experience
> with other things (like Django) has been that tracebacks would be logged
> by uwsgi without any extra configuration.
>
> Thanks!
>
> _______________________________________________
> uWSGI mailing list
> [email protected]
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
This thread should help:
http://flask.pocoo.org/mailinglist/archive/2012/1/27/catching-exceptions-from-flask/#63834cbe38bacfb0f01996b7ef7f8a4a
--
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
