[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] transfer plugin exit codes



Not strict at all -- OSG uses 11 in one of our plugins to indicate a "retryable" failure.  Any nonzero exit code results in a hold with the HoldReasonSubCode being the exit code left shifted by 8 (so multiplied by 256).  We have a PeriodicRelease that retries the job after a random delay in case it was one of these failures.

-Mat

On 11/15/2022 8:25 AM, Thomas Hartmann wrote:
Hi all,

quick question on transfer plugins - how strict is the constraint on
exit codes 0,1,2? According to
https://htcondor.readthedocs.io/en/latest/admin-manual/setting-up-special-environments.html#enabling-the-transfer-of-files-specified-by-a-url
these three exit codes are the (only?) expected ones by Condor.

Potentially, I would like to distinguish between a few fail reasons,
e.g., if a file is not present vs a file only nearline. So that one
could send a job back into hold and maybe release it later on if a file
was nearline but not release it, if not found in the namespace. I.e.,
evaluating `HoldReasonSubCode` occasionally.

Cheers,
    Thomas


_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/