Database configuration error with time mismatch

[wtempel]

@yrguo

Is there anything I could do from this point?

There may be ways to recover the database with some lower-level mongo commands, but I am not familiar with them. My next recommendation would, unfortunately, be a database rebuild.

@wtempel

1. updating the CRYOSPARC_DB_PATH= definition inside /XXX/cryosparc_master/config.sh with a new, suitable path.
2. then running
   cryosparcm start
   which should start CryoSPARC with a blank database.
3. re-creating CryoSPARC users in the database with
   cryosparcm createuser
   commands (guide )
4. registering CryoSPARC workers in the database with
   cryosparcw connect commands (on the worker(s), guide ) or
   cryosparcm cluster connect command(s) (guide ), as applicable.
5. attaching project directories. You may have to delete the cs.lock file from any given project directory before attachment because the instance id stored in the new, blank database differs from the old instance id stored in the old database. This is an exception from the rule that cs.lock files should generally not be deleted.