Re: [HTCondor-users] HTCondor can't execute the job with error: Error: can't find resource with ClaimId

["Dmitry A. Golubkov" <dmitry.golubkov@xxxxxxxxxxxxxx>]

Dear Todd,

> Do you mean submit one job at some time and another 15 
minutes later?
Exactly.


> Otherwise, I would check to make sure you're not accidentally running two negotiators.
There is one negotiator. After some prints in the source code, at now I understand the following: the schedd executes the first job on dynamic slots, CLAIM_WORKLIFE = 0 in my configuration (to re-create slots each time), but the schedd tries to execute the next job on already expired slots, why it does so, I'm still investigating.



----- Original Message -----
From: "Todd L Miller" <tlmiller@xxxxxxxxxxx>
To: "HTCondor-Users Mail List" <htcondor-users@xxxxxxxxxxx>
Cc: "Dmitry Golubkov" <dmitry.golubkov@xxxxxxxxxxxxxx>
Sent: Friday, June 18, 2021 10:49:12 PM
Subject: Re: [HTCondor-users] HTCondor can't execute the job with error: Error: can't find resource with ClaimId

> An interesting observation, if you wait and start jobs not immediately, 
> but with an interval of 15-20 minutes, then the error does not occur. Or 
> is it just my luck? Still need help, please, any ideas?

 	I don't know what you mean by "start jobs not immediately, but 
with an interval."  Do you mean submit one job at some time and another 15 
minutes later?

 	It looks like you're trying run jobs in the parallel universe, so 
I really don't know.  Otherwise, I would check to make sure you're not 
accidentally running two negotiators.

- ToddM