Jobs queue but never do anything

open

#1

Fresh standalone install of v2.11 which didn’t bark any errors.

However, when I make a job it just goes into a queue and then nothing.

I don’t see anything but blank tables on the Resource Manager.

cryosparcm log command_core yields

[EXPORT_JOB] :    Exporting all job's streamlog events...
[EXPORT_JOB] :    Done. Exported 1 files in 0.00s
[EXPORT_JOB] :    Exporting job metafile...
[EXPORT_JOB] :    Done. Exported in 0.00s
[EXPORT_JOB] :    Updating job manifest...
[EXPORT_JOB] :    Done. Updated in 0.00s
[EXPORT_JOB] : Exported P1 J7 in 0.01s
Indexing /home/Documents/test/all.star ----
Base path:  /home/Documents/test
Indexing /home/Documents/test/ ----
Base path:  /home/Documents/test/
Indexing /home/Documents/test/ ----
Base path:  /home/Documents/test/
Indexing /home/Documents/test/ ----
Base path:  /home/Documents/test/
particle_blob_path path
Setting parameter J7.particle_blob_path with value /home/Documents/test/ of type <type 'str'>
[EXPORT_JOB] : Request to export P1 J7
[EXPORT_JOB] :    Exporting job to /home/Documents/test/P1/J7
[EXPORT_JOB] :    Exporting all of job's images in the database to /home/Documents/test/P1/J7/gridfs_data...
[EXPORT_JOB] :    Done. Exported 0 images in 0.00s
[EXPORT_JOB] :    Exporting all job's streamlog events...
[EXPORT_JOB] :    Done. Exported 1 files in 0.00s
[EXPORT_JOB] :    Exporting job metafile...
[EXPORT_JOB] :    Done. Exported in 0.00s
[EXPORT_JOB] :    Updating job manifest...
[EXPORT_JOB] :    Done. Updated in 0.00s
[EXPORT_JOB] : Exported P1 J7 in 0.01s

Any ideas on what to try?


#2

Hi @t.laughlin,

Did you connect a worker node to queue jobs to? Follow this guide here for more information (especially the last part of this section) https://cryosparc.com/docs/reference/install/#worker


#3

Sorry for the late reply. Does the worker need to be connected even if it is the same workstation as the master?


#4

Hi @t.laughlin,

Yes, you still need to run the cryosparcw connect command to let the master process know about the compute resources available on the machine.


#5

connecting the worker definitely appears to be the issue, but I’m getting a error when I attempt to connect it

Traceback (most recent call last):
  File "bin/connect.py", line 222, in <module>
    gpu_devidxs = check_gpus()
  File "bin/connect.py", line 104, in check_gpus
    num_devs = print_gpu_list()
  File "bin/connect.py", line 22, in print_gpu_list
    import pycuda.driver as cudrv
ImportError: No module named pycuda.driver