Database Spawn error when other users start cryosparcm

I am trying to install a centralized cryosparc master that everyone in my lab can access. We set it up in a shared folder, but only the account that installed cryosparc can run the cryosparcm start command. If anyone else tries to start the master, they get an error:

Starting cryoSPARC System master process..
CryoSPARC is not already running.
database: ERROR (spawn error)

We tried following the instructions in Database: ERROR (spawn error) during update, and deleting the /tmp/*.sock files and killing any orphaned processes, but that doesn’t help.

The permissions for all the cryosparc files are -rwxrwxrwx.

Is it possible to set up a shared master that anyone with access can start?

Running cryosparc v3.2.0.

Hey @WGL,

Normally, you’d have the cryoSPARC instance running at all times; you shouldn’t need to stop and start it. The idea is that you’d have the users create accounts in the web interface and allow them to log in/out as they please.
If you’re not able to do that, then it’s best to instead install cryoSPARC using a shared service account that all users can su to. That way if someone ever needs to stop or start cryoSPARC, they can switch to this user and run those commands. All other commands (e.g., cryosparcm cli <command()> are available to all users with access to the cryosparc_master folder.