A few questions/comments that might help. What version of supervisor are you using?
Supervisord will create the socket. I'm not too familiar with the nginx plugin but it needs to configure an fcgi-program ( http://supervisord.org/configuration.html#fcgi-program-x-section-settings) in supervisor. If it generates a config file on disk, you could look at that and see what's there. Cheers, Roger On Tue, Aug 9, 2011 at 2:47 PM, Eric Butter <[email protected]> wrote: > Hi supervisor users; > > I am trying to serve a websocket server and a gunicorn/django wsgi app > both over nginx at the same time using supervisor subprocesses. > > The websocket subprocess (which is constantly served or restarted > using the nginx tcp patch and a background supervisor subprocess) is > working splashingly, but on http connect I cannot access the django > socket: > > upstream app_server { > server unix://path/to/gunicorn_django.sock; > } > (leaving out the details here) > server { > location / { > proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; > proxy_set_header Host $http_host; > proxy_redirect off; > # proxy_buffering off; > > if (!-f $request_filename) { > proxy_pass http://app_server; > break; > } > } > } > > I understand that I need a serverurl=/path/to/gunicorn_django.sock; I > did this, but when I tried debugging with sudo supervisord -n and > navigate to /path/to/django.sock, the socket has never been created. > What am I forgetting to do here? Why is the socket not created? > > Thanks so much for your help! > > Eric Butter > _______________________________________________ > Supervisor-users mailing list > [email protected] > http://lists.supervisord.org/mailman/listinfo/supervisor-users >
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
