Re: [Condor-users] jobs stuck in queue with X state

[Jaime Frey <jfrey@xxxxxxxxxxx>]

There is a bug in both 6.6 and 6.7 such that condor_rm -forcex will only
remove jobs with leave_in_queue evaluating to true if you specify the
exact job id (i.e. using cluster id, username, or a constraint doesn't
work). Current workarounds are to use the exact job id with condor_rm
-forcex for these jobs, or use condor_qedit to set LeaveJobInQueue to
False before running condor_rm -forcex.

-- Jaime

On Mon, 6 Dec 2004, John Wheez wrote:

> I have this same problem on my linux system as well. In older versions
> of condor I was able to remove teh job via condor_rm -forcex (username)
> but this doesn't seem to work in the latest Condor 6.7.2
>
> JW
>
>
> >
> >I can't seem to remove any jobs anymore (after adding leave_in_queue) in the
> >submit file.
> >
> >After a condor_rm <jobnumber>, the enter remove the remove state, but never
> >get removed from the queue.
> >
> >A condor_rm <jobnumber> -forcex yield the output:
> >
> >Couldn`t find/remove all jobs in cluster <jobnumber>
> >
> >Any ideas ?
> >
> >
> >
> Oliver Hotz wrote:
>
> Oliver Hotz
> Digital Supervisor / Artist
> http://www.oliverhotz.com
> ICQ: 6174819
> AIM: oliverhotz
>
>
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> http://lists.cs.wisc.edu/mailman/listinfo/condor-users
>

+----------------------------------+---------------------------------+
|            Jaime Frey            |  Public Split on Whether        |
|        jfrey@xxxxxxxxxxx         |  Bush Is a Divider              |
|  http://www.cs.wisc.edu/~jfrey/  |         -- CNN Scrolling Banner |
+----------------------------------+---------------------------------+