Good instincts Roberto -- it looks like this app is calling flask's app.run.
I think our users are going to keep doing things like this -- they port code from their own computers, and end up with stuff that tries to run its own wsgi servers... We'll keep an eye out for it, and tell people to not do it, but maybe there's a way of making uwsgi more resilient to it?
hp -- Harry Percival Developer [email protected] PythonAnywhere - a fully browser-based Python development and hosting environment <http://www.pythonanywhere.com/> PythonAnywhere LLP 17a Clerkenwell Road, London EC1M 5RD, UK VAT No.: GB 893 5643 79 Registered in England and Wales as company number OC378414. Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK On 19/01/14 12:42, Roberto De Ioris wrote:
PS - I just noticed that, when trying to do a reload for that vassal, that we also see one errors like this: emperor_respawn/write(): Broken pipe [core/emperor.c line 656] As well as the constant stream of errors saying [emperor] kill: No such process [core/emperor.c line 1682]Does this vassal has any special config ? Is it possible to have its full config (--show-config) and the logs chunk when it reloads ? For some reason this vassal closed the communication with the emperor (maybe the master crashed ?) Some time ago a user reported a similar issue and it was hosting a flask app that was binding by itself (read: calling app.run) practically overriding the master. I would give a look at it
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
