You may be able to update the cryosparc_worker/
software by adapting the steps described in Update from 4.2 to 4.5.1 failed - #4 by wtempel.
There are additional potential problems:
- Can jobs on this configuration properly communicate with CryoSPARC master processes? What is the output of the command (inside a fresh shell)
eval $(cryosparcm env) # load CryoSPARC environment curl ${CRYOSPARC_MASTER_HOSTNAME}:${CRYOSPARC_COMMAND_CORE_PORT} exit # exit the shell
- Is the
fuseblk
filesystem that holds the project directory compatible with CryoSPARC? Does it support symbolic links? - The list of target nodes may need to be deduplicated. Targets can be removed with the
remove_scheduler_target_node()
cli function.