[GE users] qconf -purge syntax

reuti reuti at staff.uni-marburg.de
Tue Oct 12 22:44:53 BST 2010


Am 12.10.2010 um 23:19 schrieb templedf:

> Are you using classic or BDB spooling?
> 
> Daniel
> 
> On 10/12/10 2:05 PM, Harry Mangalam wrote:
>> Now THAT's impressive! An instant reply direct from DanT.
>> (Take that, MS support!). :)
>> 
>> I tried a few variants of these:
>> $ qconf -purge queue   \*  long-adc at a64-101
>> $ qconf -purge queue   '*' long-adc at a64-101
>> $ qconf -purge queue   \*  long-adc at a64-101
>> $ qconf -purge "queue" '*' long-adc at a64-101
>> $ qconf -purge "queue" \*  long-adc at a64-101
>> $ qconf -purge 'queue' \*  long-adc at a64-101

I would be curious what's the definition of "long-adc" - is the host in question in a hostgroup? Do you have still some jobs running in an orphaned queue instance?

-- Reuti


>> 
>> All returned:
>> Attribute name ("*") and/or value ("a64-101") not found
>> 
>> and ..
>> $ qconf -de a64-101
>> Host object "a64-101" is still referenced in cluster queue "long-adc".
>> 
>> I should have mentioned, this is with 6.2 (no updates).  There were no
>> error messages about a bad option to qconf and the man page does refer
>> to the '-purge' option, so I'm assuming it's supported with 6.2.
>> 
>> Is there a better way to rid myself of this infestation of ghost
>> nodes?
>> 
>> Harry
>> 
>> 
>> On Tuesday 12 October 2010 13:46:35 Daniel Templeton wrote:
>> 
>>> Try:
>>> 
>>> qconf -purge queue \*<queue>@<host>
>>> 
>>> Note that the first "queue" is literal.
>>> 
>>> Daniel
>>> 
>>> On 10/12/10 1:38 PM, hjmangalam wrote:
>>> 
>>>> I've run into the dreaded:
>>>> 
>>>> $ qconf -de MYHOST
>>>> Host object "MYHOST" is still referenced in cluster queue
>>>> "AGGRO".
>>>> 
>>>> It's no longer actually referenced in the queue and the hostgroup
>>>> @AGGRO which defines the hosts for the Qs no longer contains it.
>>>> 
>>>> ie 'qconf -shgrp @AGGRO | grep MYHOST' returns nothing
>>>> 
>>>> the jobs that were running have been explicitly deleted and no
>>>> longer show up in a 'qstat'.
>>>> 
>>>> the only place where it still shows up in in the qmon window:
>>>> [qmon ->   Cluster Queue Control ->   Hosts] where the hosts are
>>>> listed but provide no info to SGE (they've been physically
>>>> removed).
>>>> 
>>>> The SGE wiki and qconf man page refer to the 'qconf -purge'
>>>> command as being useful in this kind of case but the syntax is
>>>> confusing.
>>>> 
>>>> Dan T's HOWTO contains the admonition:
>>>> /Chuck Norris uses qconf -purge/
>>>> 
>>>> but fails to provide an example (because Chuck Norris don't need
>>>> no stinkin examples).
>>>> 
>>>> And the qconf man page is similarly laconic in in its dearth of
>>>> examples.
>>>> 
>>>> I thought that you would use it like:
>>>> 
>>>> qconf -purge queue '*' AGGRO at MYHOST
>>>> 
>>>> but that returns:
>>>> Attribute name ("*") and/or value ("MYHOST") not found
>>>> 
>>>> Very happy to get some suggestions..
>>>> 
>>>> TIA
>>>> Harry
>>>> 
>> 
> 
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=286698
> 
> To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=286704

To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].



More information about the gridengine-users mailing list