I suspect that a “zombie” database process prevented proper startup of updated master services. This problem may also have prevented update of any workers.
For recovery, I suggest (run commands under Linux account that “owns” the CryoSPARC instance and its processes):
cryosparcm stop- Identify CryoSPARC processes that were not terminated as expected:
ps -u $USER -opid,ppid,cmd | grep -e cryosparc -e mongo - Determine the process IDs of potentially remaining
supervisordandmongodprocesses and, if such processes exist, terminate them
kill -TERM <process id>
(but notkill -KILLorkill -9), wait 10 seconds and confirm that no CryoSPARC related processes, such assupervisordormongodremain:
ps -u $USER -opid,ppid,cmd | grep -e cryosparc -e mongo(again) cryosparcm start
If CryoSPARC startup succeeds, manually update the worker(s) according to “cluster” instructions. Otherwise, report any error messages here.