thanks TJ !
I did not try new recipe yet, but a quick attempt to gain quicker feedback via condor_job_router_into failed [1].
I found similar reports in the archives[2], but no solution. I
also found your nice slides in
https://indico.cern.ch/event/1059494/contributions/4532568/attachments/2315533/3941565/2021-09-24.htcondor-ce-5-jr-transforms.pdf
and had a peek at https://htcondor.com/htcondor-ce/v23/troubleshooting/debugging-tools/#condor_ce_job_router_info but did not found how to make that command print some info.
What am I missing ?
Stefano
[root@vocms059 config.d]# condor_q 10002553
-- Schedd: crab3@xxxxxxxxxxxxxxxx : <188.184.103.189:30735?...
@ 11/20/24 09:52:08
ID OWNER SUBMITTED RUN_TIME ST PRI SIZE
CMD
10002553.0 belforte 11/19 17:58 0+00:00:00 I 0 0.0
sleep.sh 1
Total for query: 1 jobs; 0 completed, 0 removed, 1 idle, 0
running, 0 held, 0 suspended
Total for all users: 31 jobs; 0 completed, 0 removed, 28 idle, 3
running, 0 held, 0 suspended
[root@vocms059 config.d]# condor_q 10002553 -l |
condor_job_router_info -match-jobs -ignore-prior-routing -jobads
-
Matching jobs against routes to find candidate jobs.
[root@vocms059 config.d]#
[2]
https://www-auth.cs.wisc.edu/lists/htcondor-users/2022-May/msg00065.shtml
https://www-auth.cs.wisc.edu/lists/htcondor-users/2022-May/msg00018.shtml
I musunderstood. you can use condor_job_router_info if the router is not a CE.