Command_core: OSError: [Errno 2] No such file or directory at get_gpu_info_run()

cryosparc v2.12.14 on centos 7.7
I am getting the following error message in comand_core.log

*** BG WORKER START
[POST-RESPONSE-THREAD ERROR  2019-12-18 12:10:51.267004  at  get_gpu_info_run ]
-----------------------------------------------------
Traceback (most recent call last):
  File "cryosparc2_command/command_core/__init__.py", line 145, in run
    self.target(*self.args)
  File "cryosparc2_command/command_core/__init__.py", line 873, in get_gpu_info_run
    print subprocess.check_output(["ls /home_local/hpc/cryosparc2/cryosparc2_worker/deps/anaconda/bin/python /home_local/hpc/cryosparc2/cryosparc2_m
aster/cryosparc2_compute/get_gpu_info.py"])
  File "/home_local/hpc/cryosparc2/cryosparc2_master/deps/anaconda/lib/python2.7/subprocess.py", line 216, in check_output
    process = Popen(stdout=PIPE, *popenargs, **kwargs)
  File "/home_local/hpc/cryosparc2/cryosparc2_master/deps/anaconda/lib/python2.7/subprocess.py", line 394, in __init__
    errread, errwrite)
  File "/home_local/hpc/cryosparc2/cryosparc2_master/deps/anaconda/lib/python2.7/subprocess.py", line 1047, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory
[..]

If I modified Line869 of cryosparc2_master/cryosparc2_command/command_core/init.py

[..]
try:
                    #value = subprocess.check_output(full_command, stderr=subprocess.STDOUT)
                    value = subprocess.check_output(full_command, stderr=subprocess.STDOUT,shell=True)
[..]

the error message disappears and final_gpu_info seems to get correct value for our system

[{u'mem': 11996954624, u'id': 0, u'name': u'Tesla K80'}, {u'mem': 11996954624, u'id': 1, u'name': u'Tesla K80'}, {u'mem': 11996954624, u'id': 2, u'n
ame': u'Tesla K80'}, {u'mem': 11996954624, u'id': 3, u'name': u'Tesla K80'}, {u'mem': 11996954624, u'id': 4, u'name': u'Tesla K80'}, {u'mem': 119969
54624, u'id': 5, u'name': u'Tesla K80'}, {u'mem': 11996954624, u'id': 6, u'name': u'Tesla K80'}, {u'mem': 11996954624, u'id': 7, u'name': u'Tesla K8
0'}]

Could you please confirm that the fix is correct?
Thank you
JC

Hi @jcducom,

This is indeed the correct fix. Thanks for your help! I’ll push this out in the next release.