Open jean997 opened 3 years ago
I haven't seen that one before. @gaow have you?
Hmm I have not seen it in the past. Can we first make sure all the previous dsc
commands have been terminated on that node that submitted the job? eg you can try to go on that node and use top
to see if they are not terminated properly, and kill then retry, if that's the case?
I had been running dsc on a node in an interactive session and I terminated the session and restarted before trying again. I think that should have effectively stopped anything running right? I have it running again now because I added yet another module. It may be a while before it gets to the partially completed module. I will let you know how it comes out. Thanks!
This problem never resurfaced so I can't replicate it. Feel free to close the issue of leave it open as you see fit.
Hi again, I have a dsc workflow that I added a module to and reran to run the extra module. About half of the jobs for that module completed and I didn't see the rest so I re-ran the DSC command thinking something had happened and the command had died. When DSC re-runs I get lots of lines that say
ERROR: threads can only be started once
and the jobs are not submitted. This is on rcc. Thanks!