See if any of your periodic clean-up jobs could wipe out the entry from /tmp. If a directory entry was created and opened by a process, then the removal of the entry from the directory does not affect the process that holds the socket open. But any new attempt to find or open the deleted entry results in error.
This is just one possibility of what could be happening in your case. /Sergey On Thu, May 8, 2014 at 8:25 PM, Paul Fox <[email protected]> wrote: > matt's mail made me start thinking about pathnames, so i did > some more groveling. > > it seems that netstat thinks the socket is being listened on: > > # netstat -an | grep supervisor > unix 2 [ ACC ] STREAM LISTENING 8404 > /var/tmp/supervisor.sock.567 > > and it seems that supervisord still thinks it has the socket open: > # ps axf | grep '[p]ython.*supervisord' > 723 ? Ss 83:07 /usr/bin/python /usr/bin/supervisord > # ls -l /proc/723/fd | grep sock > lrwx------ 1 root root 64 May 8 19:26 4 -> socket:[8247] > lrwx------ 1 root root 64 May 8 19:26 5 -> socket:[8404] > > so i guess it's possible that some unrelated process removed the > socket from /tmp. > > i guess i'll restart supervisord, and see if it happens again. > > paul > ---------------------- > paul fox, [email protected] (arlington, ma, where it's 54.9 > degrees) > _______________________________________________ > Supervisor-users mailing list > [email protected] > https://lists.supervisord.org/mailman/listinfo/supervisor-users >
_______________________________________________ Supervisor-users mailing list [email protected] https://lists.supervisord.org/mailman/listinfo/supervisor-users
