On 25 May 2012 14:45, Fritz Ferstl <[email protected]> wrote: > Hhhhmmm ... would need to look into the code whether it even would > complain about that for a queued job. It's clear for a running job and if > that job was running before and got requeued then it would be easily > explicable, I guess. Might that be the case? > I don't think this job has ever run. Indeed it has a fun bug where it claims it can't run because each PE has only 2 billion slots. Possibly related.
It certainly hasn't run in the PE in question as that PE and the associated queue were only created so I could test something out. The hosts on which the queue existed had a very restrictive projects setting. William > > Fritz > > Am 25.05.2012 um 15:24 schrieb William Hay: > > On 25 May 2012 14:00, Fritz Ferstl <[email protected]> wrote: > > Hi William, > > > remove it from the queue's pe_list. Then wait for the job(s) to finish > and > > you can delete it. > > > I deleted the only queue that referenced it. There were no jobs in > the PE or the queue > that had referenced it. The job it complained about was in 'qw' state > but the pe wildcard > it requested matched the name of the PE I wanted to delete as well as > ones I want to keep. > > > William > > > [image: Univa]Fritz Ferstl | CTO and Business Development, EMEA > Univa Corporation <http://www.univa.com/> | The Data Center Optimization > Company > E-Mail: [email protected] | Phone: +49.9471.200.195 | Mobile: > +49.170.819.7390 > > [image: Where Grid Engine lives] > > >
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
