Further to this report, I tried using 19.6.0-4 from snapshot.debian.org (gunicorn & python-gunicorn) but the gunicorn service then failed to start correctly.
$ sudo service gunicorn status
● gunicorn.service
Loaded: loaded (/etc/init.d/gunicorn; generated; vendor preset:
enabled) Active: active (exited) since Thu 2016-09-29 23:07:45 BST; 6s
ago Docs: man:systemd-sysv-generator(8)
Process: 23613 ExecStop=/etc/init.d/gunicorn stop (code=exited,
status=0/SUCCESS) Process: 23615 ExecStart=/etc/init.d/gunicorn start
(code=exited, status=0/SUCCESS)
Sep 29 23:07:45 sylvester systemd[1]: Starting gunicorn.service...
Sep 29 23:07:45 sylvester systemd[1]: Started gunicorn.service.
From the /etc/init.d/gunicorn file from 19.6.0-4, it looks like the
init file is calling a helper called /usr/sbin/gunicorn-debian which
does not exist in 19.6.0-4
There was nothing helpful in the log file. We're using a gunicorn
config in /etc/gunicorn.d/lava-server.gunicorn:
CONFIG = {
'mode': 'wsgi',
'working_dir': '/var/lib/lava-server/home/',
'user': 'lavaserver',
'group': 'lavaserver',
'args': (
'--bind=127.0.0.1:8000',
'--workers=4',
'--log-file=/var/log/gunicorn/lava-server.log',
'--log-level=debug',
'lava_server.wsgi:application',
),
}
(At the time of testing, we only used --log-level=info)
I've now downgraded to gunicorn from jessie to get a working server.
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
pgpCJ1bkDwuSO.pgp
Description: OpenPGP digital signature
