accesing to my gunicorn console

Posted January 28, 2019 2.7k views
UbuntuApplicationsUbuntu 16.04

Hi, i have a running python + flask app runing in my digital ocean droplet, and it is running with ngninx and gunicorn, and so if i start my app, i can see my “gunicorn console output”

[2019-01-28 16:34:13 +0000] [3010] [INFO] Starting gunicorn 19.9.0
[2019-01-28 16:34:13 +0000] [3010] [INFO] Listening at: (3010)
[2019-01-28 16:34:13 +0000] [3010] [INFO] Using worker: sync
[2019-01-28 16:34:13 +0000] [3013] [INFO] Booting worker with pid: 3013
[2019-01-28 16:35:03 +0000] [3010] [CRITICAL] WORKER TIMEOUT (pid:3013)
[2019-01-28 16:35:03 +0000] [3013] [INFO] Worker exiting (pid: 3013)
[2019-01-28 16:35:03 +0000] [3110] [INFO] Booting worker with pid: 3110

but if i close taht ssh connection, my gunicorn will still running and working correctly but im not able to see again that console, is there a way to access to that console whit out killing gunicorn process?
i want this in order to see the errors and warnings that my gunicorn will show me

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer


Great question. There are many schools of thought and preferences on this. What I consider to be the more professional approach is to create a systemd script for starting it up and then having it write any output to a log file. That said, many people are content with the simplest answer:

screen -S gunicorn
[start command here]
control + a, then d

Then to return:

screen -r gunicorn

The “control +a, then d” part has you holding CTRL on your keyboard while pressing A, releasing A, then pressing D, and then releasing D. After releasing D, you can release CTRL. This is basically a saved shell session that persists beyond your SSH session, and can be recalled at any time.