Any ideas why my gunicorn server won\'t start?
jeffy@originaldjangster:~$ sudo /home/jeffy/django_files/django_test_venv/bin/gunicorn -c /home/jeffy/django_files
Turns out I just needed to sudo kill 3231
and sudo kill 7014
. I incorrectly thought they first needed to brought to the foreground. The fact that the processes couldn't be seen until I used the capital A option (ps -A
) mislead me, that they were somehow special.
The server was running (in the foreground) when I went to sleep before my wife. She turned off the computer before going to bed.
Ubuntu and gunicorn Newbie. Could you tell?
I have gotten used to run killall gunicorn
before (re)starting Gunicorn in my local development environment.
I also came across same problem ... Dont try to run gunicorn from su . Just change user and try again
Restarting the computer helped for me
ps -A
so I did not know what to kill
netstat -aWn --programs | grep 80
For anyone who has nothing running on the port to kill, if app.run()
is in the file gunicorn is running, then it will run twice on the port and keep attempting to retry the connection.
In my case, I was running $ gunicorn run:app where run.py had:
from app import app
app.run(debug=True)
in it. When I commented out the app.run, it worked.