The socket file does not exist. I was under the impression that supervisord
was supposed to create that file.

Yes, I am running supervisorctl as root.

On May 10, 2010 8:06 PM, "Roger Hoover" <[email protected]> wrote:

If you run "ls --l /var/run/supervisor.sock", what do you see?

Are you also running supervisorctl as root?  Maybe it doesn't have
permission to access the socket.  You can either run supervisorctl as root
or change the chmod in this section

[unix_http_server]
file=/var/run/supervisor.sock   ; path to your socket file
chmod=0777



On Mon, May 10, 2010 at 5:32 PM, Ben Davis <[email protected]>
wrote:
>
> Hi Roger.  I'...
_______________________________________________
Supervisor-users mailing list
[email protected]
http://lists.supervisord.org/mailman/listinfo/supervisor-users

Reply via email to