Issues Running Jobs in Existing CryoSPARC Projects

[szhang]

Hi all,

I recently encountered an issue with CryoSPARC affecting existing projects.

When attempting to clone a job, I receive the following error:
“Unable to clone: ServerError: Trying to set a parameter that doesn’t exist.”

If I submit a new job within an existing project, it starts on the GPU node but no data is copied to cache and it remains stuck at:
“SSD cache: using override environment variable for cache.”

However, when I create a new project using the same data, processing runs normally without any issues.

This problem occurred after a series of CryoSPARC issues. Initially, CryoSPARC became unresponsive for several hours after I initiated clearing intermediate data from two projects. I attempted to restart cryosparc which stalled at command_core: started. This was resolved by changing the port. I also upgraded to v5.0.1, but discovered it was incompatible with our cluster. I subsequently downgraded back to v4.7.1. Since then, I have been unable to run jobs in any existing projects, as described above.

Thank you for your help.

[wtempel]

Welcome to the forum @szhang. Am I assuming correctly that you are currently running CryoSPARC v4.7.1?

@szhang

“Unable to clone: ServerError: Trying to set a parameter that doesn’t exist.”

Is it possible that the job you are trying to clone was either created or last run before the latest upgrade or downgrade of your CryoSPARC installation? Cloning may not be supported for jobs that were created or changed on a CryoSPARC version other than the currently running CryoSPARC version.

@szhang

If I submit a new job within an existing project, it starts on the GPU node but no data is copied to cache and it remains stuck at:
“SSD cache: using override environment variable for cache.”

Please can you post the output of the command

cryosparcm cli "get_scheduler_targets()"