gunicorn.socket should allow to shutdown service without automatic reload on accesing IPv4 port

changed due date to November 16, 2020

changed milestone to %1.0.0

added bug label

Couple of links found during the investigation of the topic:

• https://github.com/benoitc/gunicorn/issues/1524
• https://serverfault.com/questions/892944/gunicorn-not-creating-socket-on-nginx
• https://www.freedesktop.org/software/systemd/man/systemd.socket.html

My rough understanding at this point is, that:

1. In /etc/systemd/system/gunicorn.service we specify, that gunicorn.socket shall be included:

[Unit]
Description=gunicorn daemon
Requires=gunicorn.socket
After=network.target
...

2. In the included /etc/systemd/system/gunicorn.socket, it listens to the :9000 and :8000, and will spawn the gunicorn process to react to the event (the part in italics is what I'm not certain about; it does not make a lot of sense, since the responsibility of handling/managing connections should be split across gunicorn and nginx; and here it looks like there's a third party messing with the process)

[Unit]
Description=gunicorn socket

[Socket]
ListenStream=/run/gunicorn/socket
ListenStream=0.0.0.0:9000
ListenStream=[::]:8000

[Install]
WantedBy=sockets.target

If I understand it correctly, it might be enough to remove Requires=gunicorn.socket line from /etc/systemd/system/gunicorn.service (and the /etc/systemd/system/gunicorn.socket file); but that might need to be tested.

It might be something from https://www.freedesktop.org/software/systemd/man/systemd.socket.html, too - e.g. RemoveOnStop=true

created merge request !292 (merged) to address this issue

mentioned in merge request !292 (merged)

closed with merge request !292 (merged)

mentioned in commit f449b01a