Re: [HTCondor-users] IS_OWNER not stopping jobs from running

[Andrew Pickford <andrewp@xxxxxxxxx>]

    Hi Christoph,
      
      Tried:
      
    condor_status -startd slot1@xxxxxxxxxxxxxxxxxxxxx -af is_owner 

but the output is empty. Should the option be -slot instead of -startd? In that case I get:

root@wn-choc-043:/etc/condor/config.d# condor_status -slot slot1@xxxxxxxxxxxxxxxxxxxxx -af is_owner
undefined

I was looking at using START for this sort of control as well. IS_OWNER has the disadvantage of not having access to job classad values only the machine classad values, but the advantage that the state condor_status shows goes from unclaimed to owner. While using just START leaves the machine in the unclaimed state. I was thinking of using IS_OWNER for automatic execute node health checks that something like icinga could then check for nodes in the owner state to flag errors.


Cheers,

Andrew

On 13/11/2025 10:46, Beyer, Christoph wrote:

> Hi,
>
> not sure about the IS_OWNER option but the manual quite confirm what you say it should do :) 
>
> What does 
>
> condor_status -startd slot1@xxxxxxxxxxxxxxxxxxxxx -af is_owner
>
> say ? 
>
> I think the more common option to stop jobs from starting on an EP is to add a custom variable to the START _expression_ e.g.: 
>
> START = $(START) && START_JOBS == true
>
> Then declare START_JOBS as a startd variable and make it remote settable, set the default in the config ...
>
> Best
> christoph
>
>