Abnormale Beendigung Fehler-supervisor

Ich versuche, supervisor mit nginx, aber ich habe nicht in der Lage zu bekommen, um die nginx Teil noch, weil ich bin Verschraubung etwas mit Vorgesetzten.

Kann ich

sudo supervisorctl reread

und er wird sagen: "site_demo: verfügbar". Dann Lauf ich

sudo supervisorctl update

und es sagt "site_demo: Aktualisierung der Prozess-Gruppe". So, scheint in Ordnung. Aber dann versuche ich zu laufen

sudo supervisorctl start site_demo

und ich bekomme die Fehlermeldung

site_demo: ERROR (abnormal termination)

Hier ist mein Vorgesetzter.conf-Datei:

; supervisor config file

[unix_http_server]
file=/var/run//supervisor.sock   ; (the path to the socket file)
chmod=0700                       ; sockef file mode (default 0700)

[supervisord]
logfile=/var/log/supervisor/supervisord.log ; (main log file;default $CWD/supervisord.log)
pidfile=/var/run/supervisord.pid ; (supervisord pidfile;default supervisord.pid)
childlogdir=/var/log/supervisor            ; ('AUTO' child log dir, default $TEMP)

; the below section must remain in the config file for RPC
; (supervisorctl/web interface) to work, additional interfaces may be
; added by defining them in separate rpcinterface: sections
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface

[supervisorctl]
serverurl=unix:///var/run//supervisor.sock ; use a unix://URL  for a unix socket

; The [include] section can just contain the "files" setting.  This
; setting can list multiple files (separated by whitespace or
; newlines).  It can also contain wildcards.  The filenames are
; interpreted as relative to this file.  Included files *cannot*
; include files themselves.

[include]
files = /etc/supervisor/conf.d/*.conf

Und hier ist die demo.conf, die eine Datei enthalten, die unter [include]:

[program:site_demo]

directory=/home/snorthway/demo/website

environment=PYTHONPATH=/home/snorthway/python-envs/demo

command=/home/snorthway/python-envs/demo/bin/python /home/snorthway/demo/website/manage.py runfcgi method=prefork  socket=/home/snorthway/eft/demo/fcgi/socket pidfile=/home/snorthway/eft/demo/fcgi/demo.pid minspare=4 maxspare=10 daemonize=false

redirect_stderr=true

stdout_logfile=/home/snorthway/eft/demo/logs/demo.fcgi.log

autostart=true

user=www-data

Habe ich überprüft, dass alle Wege vorhanden sind und so weiter, also denke ich nicht, dass ist das problem.

Meine log-Datei sieht wie folgt aus:

2013-06-24 15:40:23,548 CRIT Supervisor running as root (no user in config file)
2013-06-24 15:40:23,566 INFO RPC interface 'supervisor' initialized
2013-06-24 15:40:23,566 WARN cElementTree not installed, using slower XML parser for XML-RPC
2013-06-24 15:40:23,566 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2013-06-24 15:40:23,566 INFO daemonizing the supervisord process
2013-06-24 15:40:23,566 INFO supervisord started with pid 8896
2013-06-24 16:08:27,262 INFO spawned: 'site_demo' with pid 9221
2013-06-24 16:08:27,464 INFO exited: site_demo (exit status 0; not expected)
2013-06-24 16:08:28,469 INFO spawned: 'site_demo' with pid 9226
2013-06-24 16:08:28,667 INFO exited: site_demo (exit status 0; not expected)
2013-06-24 16:08:30,672 INFO spawned: 'site_demo' with pid 9231
2013-06-24 16:08:30,863 INFO exited: site_demo (exit status 0; not expected)
2013-06-24 16:08:33,870 INFO spawned: 'site_demo' with pid 9240
2013-06-24 16:08:34,077 INFO exited: site_demo (exit status 0; not expected)
2013-06-24 16:08:35,079 INFO gave up: site_demo entered FATAL state, too many start retries too quickly

InformationsquelleAutor snorthway | 2013-06-24