Bug#839183: gunicorn failures with 19.6.0-4

2016-10-01 Thread Chris Lamb
Neil Williams wrote: > > No; it really needs to run as a regular standalone process rather than > > being managed by a web browser. […] > One step at a time we have some very old code in lava-server until > at least 2017, it may not take nicely to switching away from apache. Hm? I'm not sugg

Bug#839183: gunicorn failures with 19.6.0-4

2016-09-30 Thread Neil Williams
On Fri, 30 Sep 2016 20:06:26 +0100 Chris Lamb wrote: > [Switching 839...@bugs.debian.org → 839...@bugs.debian.org] > > Hi Neil, > > Thanks for your patience and understanding; didn't mean to break your > installation and I can understand that the initscript (etc.) sticking > around would have b

Bug#839183: gunicorn failures with 19.6.0-4

2016-09-30 Thread Chris Lamb
[Switching 839...@bugs.debian.org → 839...@bugs.debian.org] Hi Neil, Thanks for your patience and understanding; didn't mean to break your installation and I can understand that the initscript (etc.) sticking around would have been rather confusing. That (ie. #839183) is now fixed. > OK - should

Processed: Re: Bug#839183: gunicorn failures with 19.6.0-4

2016-09-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 839183 gunicorn: Obsolete/confusing conffiles remain despite removal > of Debian-specific machinery in 19.6.0-3 Bug #839183 {Done: Chris Lamb } [gunicorn] gunicorn: No longer provides /etc/init.d/gunicorn so servers fail Changed Bug titl

Bug#839183: gunicorn failures with 19.6.0-4

2016-09-30 Thread Chris Lamb
retitle 839183 gunicorn: Obsolete/confusing conffiles remain despite removal of Debian-specific machinery in 19.6.0-3 clone 839183 -1 severity -1 wishlist retitle -1 gunicorn: Please provide examples on how to run gunicorn post removal of Debian-specific machinery in 19.6.0-3 thanks Neil William

Bug#839183: gunicorn failures with 19.6.0-4

2016-09-30 Thread Neil Williams
On Fri, 30 Sep 2016 10:14:28 +0100 Chris Lamb wrote: > Neil, > > > 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': 'lavaserve

Bug#839183: gunicorn failures with 19.6.0-4

2016-09-30 Thread Chris Lamb
Neil, > 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

Bug#839183: gunicorn failures with 19.6.0-4

2016-09-29 Thread Neil Williams
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: activ