Hi all, has somebody also observed jobs, that allegedly(?) have no owner and are thus skipped by the sched? We have currently two jobs, that arrived today morning on one of our CEs and got routed to Condor [1]. The Condor scheduler however has been ignoring these jobs insisting that they do not have an owner [2]. Oddly, when querying the scheduler directly, these jobs look OK regarding the owner. Installed packages look like [3] on the CE. Maybe somebody has an idea, what might be happening here? Cheers, Thomas [1] > condor_ce_q 2594831 -af Owner RoutedToJobID sgmcms 6828787.0 > condor_q 6828787.0 -af Owner RoutedFromJobId sgmcms 2594831.0 [2] > grep 6828787 condor/*Log condor/SchedLog:05/24/22 17:37:43 (pid:2172) Cluster 6828787 has no Owner attribute. Ignoring... condor/SchedLog:05/24/22 17:37:49 (pid:2172) Cluster 6828787 has no Owner attribute. Ignoring... condor/SchedLog:05/24/22 17:38:24 (pid:2172) Cluster 6828787 has no Owner attribute. Ignoring... condor/SchedLog:05/24/22 17:38:30 (pid:2172) Cluster 6828787 has no Owner attribute. Ignoring... [3] condor-9.0.11-1.el7.x86_64 condor-classads-9.0.11-1.el7.x86_64 condor-externals-9.0.11-1.el7.x86_64 condor-procd-9.0.11-1.el7.x86_64 htcondor-ce-5.1.3-1.el7.noarch htcondor-ce-apel-5.1.3-1.el7.noarch htcondor-ce-bdii-5.1.3-1.el7.noarch htcondor-ce-client-5.1.3-1.el7.noarch htcondor-ce-condor-5.1.3-1.el7.noarch htcondor-ce-view-5.1.3-1.el7.noarch python2-condor-9.0.11-1.el7.x86_64 python3-condor-9.0.11-1.el7.x86_64 on CentOS Linux release 7.9.2009 (Core) with 3.10.0-1160.62.1.el7.x86_64
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature