Forum Discussion
Frozen Job in Devcloud
- 5 years ago
Let me add (for others having the same problem) that the DevCloud team finally cancelled my pending job.
A general good advice is to always include a deadline in your batch jobs to avoid any issue with the queueing system in case something strange happen.
Do you know which server you launched the job from? If so, you can log back into the same server, you can try ps -auxw and kill -9 the job ID. Sometimes that kills the job. Make sure you use the walltime construct in batch mode so you don't time out i the future.
Thanks,
Larry
The problem is that the node s005-n005 that was running the job went down (I don't know why) and the queue system has lost the control of the job.
I cannot login to s005-n005 because it is not running.
Apparently (with admin privileges) the problem would be simply solved by running
qdel -p 18216.v-qsvr-fpga.aidevcloud