Oh nevermind. I see how queue_conf file lets you do it. Doesn't seem like the suspended queue was a mistake then. Looks like it was triggered by a bug or it was on purpose.
-----Original Message----- From: Reuti [mailto:[email protected]] Sent: Tuesday, April 10, 2012 4:02 PM To: Maes, Richard Cc: [email protected] Subject: Re: [gridengine users] grid configuration managment Hi, Am 11.04.2012 um 00:52 schrieb Maes, Richard: > Is there a log that would indicate changes made via qconf or qmon to the queue configurations? I had a situation where there was a queue on one box that went into a 'S' state. I attempted to resume the queue on this particular host and I claimed that the queue was already in a unsuspended state. So I just ended up rebooting the host and that resolved the issue. So I am unsure if it was a bug or if somebody may have inadvertently suspended the queue and I didn't have the authority to unsuspended it, or what. /opt/sge/messages didn't seem to give a clue as to who might have suspended it or why it suspended. Is there another source of information I can look at for those kinds of questions is there any subordination defined in this queue - maybe slotwise? -- Reuti _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
