Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Debugging a Flask app running in Gunicorn

I've been working on a new dev platform using nginx/gunicorn and Flask for my application.

Ops-wise, everything works fine - the issue I'm having is with debugging the Flask layer. When there's an error in my code, I just get a straight 500 error returned to the browser and nothing shows up on the console or in my logs.

I've tried many different configs/options.. I guess I must be missing something obvious.

My gunicorn.conf:

import os  bind = '127.0.0.1:8002' workers = 3 backlog = 2048 worker_class = "sync" debug = True proc_name = 'gunicorn.proc' pidfile = '/tmp/gunicorn.pid' logfile = '/var/log/gunicorn/debug.log' loglevel = 'debug' 

An example of some Flask code that borks- testserver.py:

from flask import Flask from flask import render_template_string from werkzeug.contrib.fixers import ProxyFix  app = Flask(__name__)  @app.route('/') def index():     n = 1/0     return "DIV/0 worked!" 

And finally, the command to run the flask app in gunicorn:

gunicorn -c gunicorn.conf.py testserver:app 

Thanks y'all

like image 717
mafrosis Avatar asked Jan 21 '12 04:01

mafrosis


People also ask

How do you debug a Flask gunicorn?

The best you can do with gunicorn is to run it with gunicorn --debug testserver:app . That gives you the trace in addition to the Internal Server Error message. However, this is just the same text trace that you see in the terminal and not the Flask debugger. Adding the if __name__ ...


1 Answers

The accepted solution doesn't work for me.

Gunicorn is a pre-forking environment and apparently the Flask debugger doesn't work in a forking environment.

Attention

Even though the interactive debugger does not work in forking environments (which makes it nearly impossible to use on production servers) [...]

Even if you set app.debug = True, you will still only get an empty page with the message Internal Server Error if you run with gunicorn testserver:app. The best you can do with gunicorn is to run it with gunicorn --debug testserver:app. That gives you the trace in addition to the Internal Server Error message. However, this is just the same text trace that you see in the terminal and not the Flask debugger.

Adding the if __name__ ... section to the testserver.py and running python testserver.py to start the server in development gets you the Flask debugger. In other words, don't use gunicorn in development if you want the Flask debugger.

app = Flask(__name__) app.config['DEBUG'] = True  if __name__ == '__main__':     app.run() 

## Tip for Heroku users: Personally I still like to use `foreman start`, instead of `python testserver.py` since [it sets up all the env variables for me](https://devcenter.heroku.com/articles/config-vars#using-foreman). To get this to work:

Contents of Procfile

web: bin/web 

Contents of bin/web, file is relative to project root

#!/bin/sh  if [ "$FLASK_ENV" == "development" ]; then         python app.py else         gunicorn app:app -w 3 fi 

In development, create a .env file relative to project root with the following contents (docs here)

FLASK_ENV=development DEBUG=True 

Also, don't forget to change the app.config['DEBUG']... line in testserver.py to something that won't run Flask in debug mode in production.

app.config['DEBUG'] = os.environ.get('DEBUG', False) 
like image 120
Nick Zalutskiy Avatar answered Oct 13 '22 03:10

Nick Zalutskiy