...
main log in
~/.cryosparc/log/run/command_core.log
Code Block title database log less ~/.cryosparc/log/run/command_core.log
supervisor log in
~/.cryosparc/log/run/supervisord.log
Code Block title database log less ~/.cryosparc/log/run/supervisord.log
database log in
~/.cryosparc/log/run/database.log
Code Block title database log less ~/.cryosparc/log/run/database.log
- if there is information that database is "node is not in primary or recovering state" i.e. below
Code Block title cryoSPARC log with error AssertionError: {'code': 500, 'data': None, 'message': "OtherError: node is not in primary or recovering state, full error: {'ok': 0.0, 'errmsg': 'node is not in primary or recovering state', 'code': 13436, 'codeName': 'NotMasterOrSecondary'}
then:
Warning title backup of cryoSPARC projects Backup all your projects and data before removing cryoSPARC database. Usually it should not be a problem to import them without backup but you should backup projects just in case. You have to remember that each cryoSPARC database start naming projects from P1, therefore it is best to backup projects to i.e.
$PLG_GROUPS_STORAGE/<your-plggteam>
space.you have to move current cryoSPARC database
Code Block title database log mv ~/.cryosparc/cryosparc_database ~/.cryosparc/cryosparc_database-$(date+"%Y-%m-%d")
rerun configuration of cryoSPARC to rebuild database
- import projects that you want working with
cryoSPARC master is consuming resources when no other jobs are running
You could run additional helper script called cryosparc_idle_watcher.sh
to check whether there are any cryoSPARC worker jobs running and finish cryoSPARC master job when there aren't any jobs for some time.
Code Block | ||
---|---|---|
| ||
cryosparc_idle_watcher.sh <timeout> |