"list index out of range" error message while trying to run job after fresh installation

I have done a fresh installation of cryo sparc 2.15.0 on CentOS7 using standalone installation
The installation seems complete. However while I try to run " import micrographs" I receive a notification on top “list index out of range”
While the job status becomes “queued” and does not change to running.
When I open up the job status log
it shows repeated instances of “License is valid.” and appears to be stuck in a loop.

[user@localhost cryosparc2_master]$ cryosparcm status
----------------------------------------------------------------------------
CryoSPARC System master node installed at
/home/user/Softwares/cryosparc/cryosparc2_master
Current cryoSPARC version: v2.15.0
----------------------------------------------------------------------------

cryosparcm process status:

app                              STOPPED   Not started
app_dev                          STOPPED   Not started
command_core                     RUNNING   pid 19108, uptime 0:11:05
command_proxy                    RUNNING   pid 19256, uptime 0:11:02
command_rtp                      STOPPED   Not started
command_vis                      RUNNING   pid 19213, uptime 0:11:03
database                         RUNNING   pid 18917, uptime 0:11:08
watchdog_dev                     STOPPED   Not started
webapp                           RUNNING   pid 19347, uptime 0:11:01
webapp_dev                       STOPPED   Not started

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

global config variables:

export CRYOSPARC_LICENSE_ID="xxx"
export CRYOSPARC_MASTER_HOSTNAME="localhost"
export CRYOSPARC_DB_PATH="/home/user/Softwares/cryosparc/cryosparc2_database"
export CRYOSPARC_BASE_PORT=39010
export CRYOSPARC_DEVELOP=false
export CRYOSPARC_INSECURE=false
export CRYOSPARC_CLICK_WRAP=true

Hi @JakcNTU,

Did you notice any errors during installation? This indicates that the worker node wasn’t connected properly, which the standalone installation should take care of. To fix this, follow the instructions here to connect your worker package. Please note that since you’re installing a standalone installation, the master_hostname and worker_hostname arguments will be the same.

Dear stephan,

Thank you so much. The problem is solved.