Spawn error when type commands 'cryosparcm restart'

Dear Cryosparc users and developers,

I appreciate your efforts for structural biology fields,
I got error like this;

[cs@lsb hpclab]$ cryosparcm restart
CryoSPARC is not already running.
If you would like to restart, use cryosparcm restart
Starting cryoSPARC System master process…
CryoSPARC is not already running.
database: ERROR (spawn error)

Could you help me to solve this error?

Best wishes,
Si Hoon

I would like to show my status;

[cs@lsb hpclab]$ cryosparcm status
CryoSPARC System master node installed at
Current cryoSPARC version: v3.2.0+210831

CryoSPARC process status:

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
webapp                           STOPPED   Not started
webapp_dev                       STOPPED   Not started


WARNING: Could NOT verify active license "xxxxxxxxxxxxxx"

License validation results:

\u2713 CRYOSPARC_LICENSE_ID environment variable is set
\u2713 License has correct format
\u2713 Insecure mode is disabled
\u2713 License server set to ""
\u2715 Connection to license server FAILED

While verifying the license, CryoSPARC encountered HTTPSConnectionPool(host='', port=443): Max retries exceeded with url: /checklicenseexists/xxxxxxxxxxxxxx (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x2b0329db4950>: Failed to establish a new connection: [Errno -2] Name or service not known'))


global config variables:

export CRYOSPARC_LICENSE_ID="xxxxxxxxxxxxxx"
export CRYOSPARC_DB_PATH="/home/cs/cryosparc/cryosparc_database"

Welcome to the forum @shpark .
Does the output of
cryosparcm log database
indicate a cause of the problem?