Database: ERROR (spawn error) after sharing admin in GUI

Hi -

I am admin of cryosparc and wanted to share admin with someone else. I set them as admin using the GUI. Cryosparc worked for 10 minutes and suddenly stopped.

When I tried to restart it, it said:
$ cryosparcm start

Starting cryoSPARC System master process..

CryoSPARC is not already running.

database: ERROR (spawn error)

when I check the status, it says:
$ cryosparcm status
----------------------------------------------------------------------------
CryoSPARC System master node installed atkiertlabs]$
/gpfs/data/bhabhaekiertlabs/local_software/CryoSparc/cryosparc2_master
Current cryoSPARC version: v3.1.0
----------------------------------------------------------------------------
Shut down
cryosparcm process status:001 svc_bhabhaekiertlabs]$ cryosparcm start
Starting cryoSPARC System master process…
app STOPPED Not started
app_dev STOPPED Not started
command_core STOPPED Not started
command_rtp STOPPED Not started
command_vis STOPPED Not started
database FATAL Exited too quickly (process log may have details)
liveapp STOPPED Not started
liveapp_dev STOPPED Not started
watchdog_dev STOPPED Not started
webapp STOPPED Not started
webapp_dev STOPPED Not started

----------------------------------------------------------------------------

global config variables:
export CRYOSPARC_HOSTNAME_CHECK="ws-0001.cm.cluster"

export CRYOSPARC_HEARTBEAT_SECONDS=300
export CRYOSPARC_LICENSE_ID="ff4f001c-f1a9-11e8-94cf-e32c50945cef"
export CRYOSPARC_MASTER_HOSTNAME="ws-0001.cm.cluster"
export CRYOSPARC_DB_PATH="/gpfs/data/bhabhaekiertlabs/local_software/CryoSparc/cryosparc2_database"
export CRYOSPARC_BASE_PORT=39100
export CRYOSPARC_DEVELOP=false
export CRYOSPARC_INSECURE=false

When I run:
$ cryosparcm log command_core
---------- Scheduler running ---------------
Jobs Queued: [(‘P104’, ‘J22’), (‘P122’, ‘J1313’), (‘P137’, ‘J317’)]
Licenses currently active : 0
Now trying to schedule J22
Need slots : {‘GPU’: 1, ‘RAM’: 1, ‘CPU’: 2}
Need fixed : {‘SSD’: False}
Master direct : False
Queue status :
Queue message :
Licenses currently active : 0
Now trying to schedule J1313
Need slots : {‘GPU’: 1, ‘RAM’: 3, ‘CPU’: 4}
Need fixed : {‘SSD’: True}
Master direct : False
Queue status :
Queue message :
Licenses currently active : 0
Now trying to schedule J317
Need slots : {‘GPU’: 1, ‘RAM’: 3, ‘CPU’: 2}
Need fixed : {‘SSD’: True}
Master direct : False
Queue status :
Queue message :
---------- Scheduler finished ---------------

Any idea what I should do, please?

Thanks,
Best,
Nicolas

ok - so I used “ps aux | grep cryosparc” to kill all active jobs, then I managed to restart cryosparc and it seems to be running.
I am not 100% sure what happened. Is it possible that if the admin & a user are accessing or looking at the same job, then it generated this type of error?
Or, if the admin is looking at a job, and the user is changing the name of the workspace, or deleting the job, or something like this?