Package: gunicorn
Version: 19.6.0-1
Severity: normal
Dear Maintainer,
The template logrotate configuration that is shipped with the gunicorn
package does not send the `USR1` signal after the logs are rotated. This
results in gunicorn processes continue writing to the rotated files.
IMHO, we should include a postrotate action in the default logrotate
configuration, in order to properly re-open the log files.
Something like the following snippet should be sufficient:
```
sharedscripts
postrotate
kill -USR1 $(cat /run/gunicorn/*.pid | xargs)
endscript
```
Regards,
Dimitris
-- System Information:
Debian Release: 8.5
APT prefers stable
APT policy: (500, 'stable'), (10, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gunicorn depends on:
ii python-gunicorn 19.6.0-1
ii python-pkg-resources 5.5.1-1
ii python-setuptools 5.5.1-1
pn python:any <none>
gunicorn recommends no packages.
Versions of packages gunicorn suggests:
pn gunicorn-examples <none>
ii python-gevent 1.0.1-2
ii python-pastedeploy 1.5.2-1
ii python-setproctitle 1.1.8-1
pn python-tornado <none>
-- Configuration Files:
/etc/gunicorn.d/django.example 1b979f1dcab39660a6387d0d9506e116 [Errno 2] No
such file or directory: u'/etc/gunicorn.d/django.example
1b979f1dcab39660a6387d0d9506e116'
/etc/gunicorn.d/wsgi.example 3a5f909a7fa2fded34bc7341ae6c9c9c [Errno 2] No such
file or directory: u'/etc/gunicorn.d/wsgi.example
3a5f909a7fa2fded34bc7341ae6c9c9c'
/etc/logrotate.d/gunicorn changed [not included]
-- no debconf information
