I am not sure of all the reasons a job might get to the Admin Hold state but I have seen it when a job tries to run but the resources it uses generate an error instead of running the job. Once they are in this state they will not be looked at by the scheduler because the job has its priority set to zero. Changing the priority to something greater than zero will put them back into the scheduling. However, if the error that caused them to fail still exists they will return to the Admin Hold state when they next try to run.
Check the log files for the failure and possible reason. Carl ----- Original Message ----- > > What does this mean? I can't find any documentation and I have > several > jobs in our queues which are getting this Reason Waiting assigned > them > automatically by SLURM. The jobs themselves appear valid, but I > can't > force them to lose this state even though there are enough nodes for > the > job open. > > -Paul Edmon- > -- -- Carl Schmidtmann Center for Integrated Research Computing University of Rochester - Our Annual CIRC Poster Session is May 10, 2013 - Visit http://www.circ.rochester.edu/poster_submission.html
