heroku django Web服务器失败

Question

I use Procfile with web: python manage.py runserver '0.0.0.0:$PORT' first time it started successfully, but after first git push it crashed with this error:

OperationalError at /

could not connect to server: Connection refused
    Is the server running on host "127.0.0.1" and accepting
    TCP/IP connections on port 5432?

restarting webrunner did not help. What's the trick? heroku logs output:

2013-11-25T23:39:56.725138+00:00 app[web.1]:   File "/app/.heroku/python/lib/python2.7/site-packages/psycopg2/__init__.py", line 164, in connect
2013-11-25T23:39:56.725138+00:00 app[web.1]:     conn = _connect(dsn, connection_factory=connection_factory, async=async)
2013-11-25T23:39:56.725138+00:00 app[web.1]: OperationalError: could not connect to server: Connection refused
2013-11-25T23:39:56.725138+00:00 app[web.1]:    Is the server running on host "127.0.0.1" and accepting
2013-11-25T23:39:56.725138+00:00 app[web.1]:    TCP/IP connections on port 5432?
2013-11-25T23:39:56.725138+00:00 app[web.1]:     return Database.connect(**conn_params)
2013-11-25T23:39:56.725138+00:00 app[web.1]: 
2013-11-25T23:39:56.872620+00:00 app[web.1]: [26/Nov/2013 00:39:56] "GET / HTTP/1.1" 500 118846

using gunicorn its says that can't find gunicorn app and app[web.1]: bash: gunicorn: command not found and heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=shrouded-falls-4631.herokuapp.com fwd="188.163.187.182" dyno= connect= service= status=503 bytes= from heroku logs and heroku ps shows crashed app[web]. Using djangos' runserver at least started at first time. But then also got crashed.

Answer 1

I do not know the exact reason, but why are you running django's runserver on heroku? Heroku uses gunicorn, which can execute the .wsgi files in your project_name/project_name folder.

Instead, use: "web: gunicorn recipe.wsgi" in the procfile, so gunicorn serves your django app. Just my 2 cents.

Also, it seems if you use 0.0.0.0:5432 or 127.0.0.1:5432, it might work.

Answer 2

Your database is not connected. Make sure you set the proper DATABASE_URL environment variable, and that you actually have a postgres plan active.

Answer 3

Thanks @user2707389, it really works only with all apps declared in requirements.txt but I don't get it why it doesn't with -r option. Anyway, fixing further Procfile and correct wsgi.py made it alive.