Geek Answers Handbook

Gunicorn and Hevent attack on a flash drive on Hereka

I updated my application on Heroku to use Flask 0.9 and the new Gevent, and since then I have not been able to get the application to work on Heroku. It works fine using python web_app.py in Procfile, but using:

 web: gunicorn web_app:app -w 3 -b 0.0.0.0:$PORT -k gevent --max-requests 250

where the entry point for the application is a file labeled web_app.py.

I reduced it to the basic "hello to the world" and yet, to disaster. I also tried without Gunicorn, running it only with the Gevent server, as described in the other servers section of the Flask documentation , but again, an instant failure. I think that either I ruined my environment, or, or my requirements. Txt is disgusting.

Here is my requirements file .txt:

 jinja2 werkzeug flask wtforms gevent gunicorn psycopg2 sqlalchemy itsdangerous flask-seasurf flask-login flask-debugtoolbar flask-sqlalchemy flask-script flask-uploads flask-failsafe requests alembic braintree cloudinary

Any help would be appreciated as it cannot handle any meaningful traffic using the default server in Flask. Is there any additional information I have to provide?

EDIT:

Here is the error

 app/web.1: 2012-12-08 21:18:22 [7] [INFO] Booting worker with pid: 7 app/web.1: 2012-12-08 21:18:22 [7] [INFO] Worker exiting (pid: 7) app/web.1: 2012-12-08 21:18:22 [6] [INFO] Worker exiting (pid: 6) app/web.1: 2012-12-08 21:18:22 [5] [INFO] Worker exiting (pid: 5) app/web.1: Traceback (most recent call last): app/web.1: File "/app/.heroku/venv/bin/gunicorn", line 12, in <module> app/web.1: load_entry_point('gunicorn==0.14.6', 'console_scripts', 'gunicorn')() app/web.1: File "/app/.heroku/venv/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py", line 32, in run app/web.1: WSGIApplication("%prog [OPTIONS] APP_MODULE").run() app/web.1: File "/app/.heroku/venv/lib/python2.7/site-packages/gunicorn/app/base.py", line 124, in run app/web.1: Arbiter(self).run() app/web.1: File "/app/.heroku/venv/lib/python2.7/site-packages/gunicorn/arbiter.py", line 185, in run app/web.1: self.halt(reason=inst.reason, exit_status=inst.exit_status) app/web.1: File "/app/.heroku/venv/lib/python2.7/site-packages/gunicorn/arbiter.py", line 280, in halt app/web.1: self.stop() app/web.1: File "/app/.heroku/venv/lib/python2.7/site-packages/gunicorn/arbiter.py", line 328, in stop app/web.1: self.reap_workers() app/web.1: File "/app/.heroku/venv/lib/python2.7/site-packages/gunicorn/arbiter.py", line 419, in reap_workers app/web.1: raise HaltServer(reason, self.WORKER_BOOT_ERROR) app/web.1: gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3>

In this regard, I took out all the press statements that I mistakenly left, and this did not help at all.

+4
source share
1 answer

I just used the solution for the Heroku-fails-to-start-my-app-but-foreman-start-works question. If people are wondering, I included the application in this method call:

 @failsafe def create_app(): from routes import app return app

and structured my profile as indicated in this answer:

 web: gunicorn legalkin_app:create_app\(\) -w 3 -b 0.0.0.0:$PORT -k gevent --max-requests 250

Side note, I did something dumb to do this, but I have no idea what it is.

+2
source

More articles:


All Articles