no more gunicorn startup by default in debian/raspian 9
Posted: Wed Feb 20, 2019 5:09 pmHi, I updated my raspberry pi to the latest raspian based on debian 9 stretch, as part of the upgrade there are a number of warnings about deprecated stuff. Relevant to alarmdecoder it seems they removed the gunicorn systemd stubs, and those have to be done manually now. Looking at the alarmdecoder site I dont' see any instructions for this, so was wondering if there are some, othwerwise I'm going to have to write a systemd stub for it.
Is there a configuration that you have ?
In the meantime I am starting it up by hand:
Here is the notice during the jessie->stretch upgrade:
Is there a configuration that you have ?
In the meantime I am starting it up by hand:
/usr/local/bin/gunicorn --log-file /tmp/gunicorn.log -D --chdir /opt/alarmdecoder-webapp --worker-class=socketio.sgunicorn.GeventSocketIOWorker wsgi:application --timeout=120 --env=POLICY_SERVER=0
Here is the notice during the jessie->stretch upgrade:
gunicorn (19.6.0-3) unstable; urgency=medium
The /etc/gunicorn.d (and related usr/sbin/gunicorn{,3}-debian) scripts were
removed in 19.6.0-3 due to inflexibility, lack of documentation, not
adopted/supported upstream, did not work with virtualenvs, etc.
They were dropped prior to the stretch release to avoid having to support it
for another full release.
Users relying on this feature should invoke gunicorn manually. For an example
systemd .service file, please see the ``gunicorn-mysite.service`` file in the
gunicorn-examples package or a process manager such as runit, etc.