joan perez esteban wrote: > Hi, > not sure if I am sending this twice, my mail server returned me an error. > I did try restart the service but the error persist, I don’t have > the required file so it returns an error, > > [root@nimbusNode ~]# service supervisor stop > [root@nimbusNode ~]# service supervisor start > [root@nimbusNode ~]# supervisorctl reread > error: <class 'socket.error'>, [Errno 2] No such file or directory: file: > <string> line: 1 > [root@nimbusNode ~]# supervisorctl update > error: <class 'socket.error'>, [Errno 2] No such file or directory: file: > <string> line: 1 > [root@nimbusNode ~]# supervisorctl > unix:///tmp/supervisor.sock no such file > supervisor> exit > [root@nimbusNode ~]# > > supervisor.sock does not exist, so getting an error. Any other ideas?
i see. your symptom is different than mine. in my case, when i restarted supervisord, the socket came back, and remained there for days or weeks, and then it would disappear again. in your case, the socket is missing right away. i don't have any more to say -- sorry. paul > > many thanks in advance. > > Juan > > > > > On 25 Jan 2015, at 04:07, Paul Fox <p...@foxharp.boston.ma.us> wrote: > > > hussain wrote: > >> Hello > >> > >> I guess the error occurs because supervisor service is not running. > > > > i can't speak for juan, but that was not true in my case. the web > > interface worked fine -- all managed processes were running, and i > > could interact with supervisord from a browser. it was only the > > unix domain socket that had been somehow removed, and prevented > > supervisorctl from working. > > > > paul > > > >> > >> Do - > >> Sudo service supervisor start or > >> Sodo /etc/supervisor start > >> > >> Then run supervisorctl. > >> > >> I haven't tested this. > >> > >> Regards, > >> Hussain > >> On 25 Jan 2015 03:36, "Paul Fox" <p...@foxharp.boston.ma.us> wrote: > >> > >>> joan perez esteban wrote: > >>>> Hi all, > >>>> > >>>> I am trying to start supervisorctl but all the time I get the same > >>> error: unix:///tmp/supervisor.sock no such file. > >>>> I haven’t found anything out there that can cause that error as I am > >>> running last version. > >>>> > >>>> I am running supervisor in a centos server over a vm. > >>> > >>> i reported this exact symptom (running on ubuntu) back in may of last > >>> year. i assume my report is in the archives. glad i wasn't imagining > >>> it. :-) it happened to me several times, and since i had no real > >>> means of debugging it, i switch to "serverurl=http://127.0.0.1:9001"; > >>> in my config, to use a non-unix socket. > >>> > >>> paul > >>> > >>>> > >>>> Thanks, > >>>> > >>>> Juan > >>>> _______________________________________________ > >>>> Supervisor-users mailing list > >>>> Supervisor-users@lists.supervisord.org > >>>> https://lists.supervisord.org/mailman/listinfo/supervisor-users > >>> > >>> =---------------------- > >>> paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 26.4 > >>> degrees) > >>> _______________________________________________ > >>> Supervisor-users mailing list > >>> Supervisor-users@lists.supervisord.org > >>> https://lists.supervisord.org/mailman/listinfo/supervisor-users > >>> > > > > =---------------------- > > paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 24.1 > > degrees) =---------------------- paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 7.9 degrees) _______________________________________________ Supervisor-users mailing list Supervisor-users@lists.supervisord.org https://lists.supervisord.org/mailman/listinfo/supervisor-users
