Hi! On Wed, Sep 28, 2011 at 1:05 PM, Chris Lamb <[email protected]> wrote: >> When using a config file in /etc/gunicorn.d/ for starting gunicorn >> workers to serve a Django application, the workers crash and are >> constantly restarted because they cannot find the settings.py IF the >> apps path is given both as CONFIG['environment']['PYTHONPATH'] and as >> CONFIG['working_dir']. > > Can you reproduce just using "/usr/bin/gunicorn" directly? I can't seem > to reproduce either way.
No, I cannot, unfortunately. Only when using it with the init-script (config attached). When I activate the commented-out line, the workers constantly crash and restart. I am not 100% sure it has to do with the settings.py not found - there are no tracebacks or errors in /var/log/gunicorn/dict.conf.log except: 2011-09-29 12:10:31 [6836] [INFO] Booting worker with pid: 6836 2011-09-29 12:10:31 [6836] [INFO] Worker exiting (pid: 6836) But I tried running it manually the same way the init-script does (but without --daemon) and I get: root@vald:/etc/gunicorn.d# /usr/bin/python /usr/bin/gunicorn_django --pid /varun/gunicorn/dict.conf.pid --name dict.conf --user vald --group vald --log-file /var/log/gunicorn/dict.conf.log --bind=unix:/tmp/vamdcdict-gunicorn.sock --workers=3 --timeout=60 Settings file '/etc/gunicorn.d/settings.py' not found in current folder. Settings file '/etc/gunicorn.d/settings.py' not found in current folder. Settings file '/etc/gunicorn.d/settings.py' not found in current folder. ... Best wishes thomas
dict.conf
Description: Binary data
