Starting flower via supervisorctl... doesn't seem to work until I restart it? about flower HOT 3 CLOSED

actually it doesn't work properly after restarting it either, after a couple of clicks I get the same symptoms (browser stuck endless loading, nothing happens). I've tried this a bunch of times - supervisorctl restart enc-flower works briefly, stops, restart, works briefly, stops.

My /etc/supervisor.d/enc-flower.conf looks like:

[program:enc-flower]
command=/path/to/my/virtual/env/bin/python manage.py celery flower
process_name=%(program_name)s
numprocs=1
numprocs_start=0
autostart=false
autorestart=true
startsecs=1
startretries=3
exitcodes=0,2
stopsignal=TERM
stopwaitsecs=10
user=vagrant
redirect_stderr=false
stdout_logfile=AUTO
stdout_logfile_maxbytes=50MB
stdout_logfile_backups=10
stdout_capture_maxbytes=0
stdout_events_enabled=false
stderr_logfile=AUTO
stderr_logfile_maxbytes=50MB
stderr_logfile_backups=10
stderr_capture_maxbytes=0
stderr_events_enabled=false
directory=/path/to/my/django/project
serverurl=AUTO

I don't see any errors in the supervisord or stderr logs.

from flower.

RabbtMQ Management Console works fine BTW, so it's something specific to Celery/Flower

from flower.

well the problem seems to have magically resolved itself... maybe the cause was in Vagrant, or the browser, or this crappy Ubuntu dev box, but I guess it's not in Flower

from flower.