This happens to me quite often in different blocks, which for some reason disappear in the supervisord socket file. They did not investigate if this was due to an error or for another reason, but I am wondering if it is possible to recreate / reconnect to this socket processed by supervisord. The process is still working and I see it
> lsof -c supervisord
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
[...]
superviso 16886 root 3w REG 9,1 85344 2753325 /var/log/supervisor/supervisord.log
superviso 16886 root 4u unix 0xffff880059691800 0t0 3662006852 /var/tmp/supervisor.sock.16883
superviso 16886 root 5u unix 0xffff88017c6f7c00 0t0 3661998412 socket
[...]
But the file /var/tmp/supervisor.sock.16883 does not exist. Is there a way to recreate the socket file handled by this supervisor process? I know that I can restart the dispatcher, but I would like to avoid it.
source
share