[HTCondor-users] How to delete a paused late materialization factory

[Jeff Templon <templon@xxxxxxxxx>]

Yo,

We had some stuff in the job transform that did not take late materialisation into account - running the same transform twice on an Ad had unforeseen consequences.

Thatâs been fixed, however weâre stuck with some factories we canât get rid of:

ââ[$] condor_q -factory

-- Schedd: taai-007.nikhef.nl : <145.107.7.246:9618?... @ 12/12/24 15:36:32

 ID         OWNER            SUBMITTED  LIMIT PRESNT   RUN    IDLE   HOLD NEXTID MODE DIGEST

1191726.    templon        12/12 13:17     93      0      0      0      0      0 Norm /var/spool/condor/1726/condor_submit.1191726.digest

1191764.    templon        12/12 13:38     93      0      0      0      0      0 Gone /var/spool/condor/1764/condor_submit.1191764.digest

1192083.    templon        12/12 15:23     93      4      4      0      0     93 Done /var/spool/condor/2083/condor_submit.1192083.digest

1192085.    templon        12/12 15:23    208    102     82     20      0    203 Norm /var/spool/condor/2085/condor_submit.1192085.digest

1192088.    templon        12/12 15:24     20      2      2      0      0     20 Done /var/spool/condor/2088/condor_submit.1192088.digest

1192089.    templon        12/12 15:24    223    100     80     20      0    213 Norm /var/spool/condor/2089/condor_submit.1192089.digest

The first couple of these are such factories that got into some âpausedâ state due to materialisation errors.  I canât get rid of them:

condor_rm does not work, nor condor_release, nor condor_continue . Each such attempt generates a line in the schedd log like

SchedLog:12/12/24 15:22:36 (pid:2850107) Pausing job factory 1191726 <empty> code=3

A side note : the meaning of the âMODEâ column above is not contained in the documentation.

Let us know how to rid ourselves of these factories and thanks,

JT