Hi @kortal,
This might be the cause of your original issue. This can also cause the error message you posted below, since the UNIX sock file exists on the filesystem, but the node trying to execute the cryosparcm command doesn’t have access to the actual process itself.
Please take a look at this post:
Deleting the CRYOSPARC_MASTER_HOSTNAME variable from the config.sh file will allow you to use cryoSPARC in an environment where the host is not guaranteed across SSH sessions. Your workflow would be to turn on cryoSPARC, do some processing, then turn it off once you’re done.
I realize this may be tedious, but your other option would be to request a dedicated node where you can install cryoSPARC and keep it running for long periods of time.
For your current problem, try deleting the file mentioned, then kill off any processes that relate to cryoSPARC by using
ps -ax | grep "supervisor"
kill <pid of process>