[GE users] nodes with no jobs running after qdel but stuck in 'd' state

Wilfred Li wilfred at sdsc.edu
Wed May 24 15:41:32 BST 2006


Yes! That did it. It makes sense now. 

No job is being deleted ('d') since there is no job id in the queue, it
must have been just disabled (another 'd'). 

Regards,
 
Wilfred

-----Original Message-----
From: Reuti [mailto:reuti at staff.uni-marburg.de] 
Sent: Wednesday, May 24, 2006 8:59 PM
To: users at gridengine.sunsource.net
Subject: Re: [GE users] nodes with no jobs running after qdel but stuck
in 'd' state

Is a queue with d labeled,
it's most likely disabled.
Try to enable the queue,
and your dreams come true.

qmod -e all.q at compute-1-26.local

-- Reuti


Am 24.05.2006 um 11:56 schrieb Wilfred Li:

> Hi, all,
>
> We have some nodes that are showing jobs being deleted, but seem to be
> stuck in that state.
>
> all.q at compute-1-26.local       BIP   0/2       0.00     lx26- 
> x86      d
>
> How do we fix this? Restarting compute node sgeexecd didn't help.
> Couldn't find any spool files either, but maybe wasn't looking in the
> right place. Google didn't help either.
>
> Thanks in advance!
>
> Regards,
>
> Wilfred
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list