CryoSPARC installation stuck at "command_core: started"

Install, Configure and Update
7

Thanks @Tamino. The topic Cryosparc not starting looks similar to your situation. Assuming that the --standalone installation was disrupted just after the installation of the cryosparc_master/ package, you may consider

  1. adding the line
    export NO_PROXY="${CRYOSPARC_MASTER_HOSTNAME},localhost,127.0.0.1"
    to the file
    /home/cemkguest/software/cryosparc/cryosparc_master/config.sh
    somewhere below the definition of CRYOSPARC_MASTER_HOSTNAME
  2. restarting CryoSPARC.
    The following steps would have been performed automatically in case of a smooth
    --standalone installation.
  3. creating the first user
  4. installing the cryosparc_worker/ package
  5. adding the line
    export NO_PROXY="phobos,localhost,127.0.0.1"
    to the file
    cryosparc_worker/config.sh
    (In case the master hostname changes from phobos in the future, phobos needs to be changed accordingly in the NO_PROXY definition.)
  6. connecting the worker component with a command like
    cryosparc_worker/bin/cryosparcw connect --master phobos --worker phobos --port 99999 --ssdpath /path/to/cache
    where the --port parameter needs to be changed from the nonsensical 99999 value to the CRYOSPARC_BASE_PORT value inside
    /home/cemkguest/software/cryosparc/cryosparc_master/config.sh
    and the --ssdpath parameter points to the actual path to be used for particle caching (or is replaced altogether with --nossd)