sergey wrote:
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
i'm running a relatively old version of supervisor, so if this has
been fixed in a later release, i'll live with it -- upgrading this
particular system is difficult at the moment.
i have a supervisord process that's been running for over 32 days,
since april 6th. it's still running, and will
matt wrote:
I’d suggest checking your /etc/supervisord.conf to be sure that the
following two config entries match up:
[unix_http_server]
file=/tmp/supervisord.sock ; (the path to the socket file)
[supervisorctl]
serverurl=unix:///tmp/supervisord.sock
they match.
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
