The database may be corrupted.
You may want to investigate possible causes of a putative database corruption, such as:
- did the volume that holds
/ourdisk/hpc/bsc/cryosparc/cryosparc_databaserun out of space at some point? - is the wiredtiger mongo engine supported on the filesystem? To find out the type of the filesystem, you can run
stat -f /ourdisk/hpc/bsc/cryosparc/cryosparc_database. - did the computer shut down due to a power failure?
To recover, you may want to
- eliminate the cause of the (hypothetical) database corruption
- then either restore a recent backup of your database, if avalable,
- or restore your CryoSPARC instance starting from a fresh database as described in Could not get database status - #13 by wtempel