Database: ERROR (spawn error)

Troubleshooting
15

I run into these errors a few times:

Earlier, every time, this got taken care of by following.

  1. ps -ax | grep cryosparc

  2. cryosparcm stop

  3. Again, run ps -ax | grep cryosparc if you get any processes running, then you can take two actions
    a) killall -u $(whoami) python on workstation or HPC, this should kill all processes; however, if you again find any processes running in the background after checking ps -ax | grep cryosparc, then try using step b)
    b) Shut down the workstation or request the HPC administrator to kill all your processes or request them to restart your login again.

  4. Once restart of master node executed, take the advised procedure in this thread as follows:

a) Take a backup of your cryosparc_database in another directory, then change the present cryosparc_database name as cryosparc_database.old/cryosparc_database_old.
b) restart your cryosparc instance using cryosparcm start; this will create a new cryosparc_database.
c) The new database may not be useful as this may not have any information about any users or data saved and analyzed earlier. Now delete new database and change the cryosparc_database.old/cryosparc_database_old as cryosparc_database. Make sure your backup database has the same memory. Before going further, make sure you have a backup of cryosparc_database.old/cryosparc_database_old in another directory.
d) Enter the cryosparc_database and run following two commands separately as follows
eval $(cryosparcm env)
mongod --dbpath ./ --repair

These steps may repair your database error and restore your database and previous up and running cryosparc instance completely.

I hope this may be useful. Thanks to the several related Threads and Developers. I could restore mine, and I am sure you may also be able to restore your cryosparc instance up and running!

1 Like