Re: [HTCondor-users] debug condor_starter

["Beyer, Christoph" <christoph.beyer@xxxxxxx>]

Hmm,

that seems to be a different problem, can you start it from the command line and maybe give it a strace ? 

Best
christoph

-- 
Christoph Beyer
DESY Hamburg
IT-Department

Notkestr. 85
Building 02b, Room 009
22607 Hamburg

phone:+49-(0)40-8998-2317
mail: christoph.beyer@xxxxxxx

----- UrsprÃngliche Mail -----
Von: "Antonio Falabella" <antonio.falabella@xxxxxxx>
An: "HTCondor-Users Mail List" <htcondor-users@xxxxxxxxxxx>, "Christoph Beyer" <christoph.beyer@xxxxxxx>
Gesendet: Donnerstag, 8. Mai 2025 10:23:20
Betreff: Re: [HTCondor-users] debug condor_starter

Dear Christoph,

the point is the even if I revert to my original configuration I keep 
seeing this line in the StarterLog

05/08/25 10:17:41 (pid:1964040) **** condor_starter (condor_STARTER) pid 
1964040 EXITING WITH STATUS 1

which I am not able to debug let's say "out of the box" to understand 
the source of the exit status code 1.

Thanks

Antonio

On 07/05/25 15:30, Beyer, Christoph wrote:
> Hi Antonio,
>
> if you want to use the custom attribute in the start expression you must declare it being a startd_attribute - I think, try:
>
> STARTD_ATTRS = $(STARTD_ATTRS), CustomStatus
>
> Also you might want it to set static in the config as there might pe a short period at the start of the machine were condor_cron has not run yet but condor is already running, put
>
> CustomStatus = "foo"
>
> Or as an alternative solution to that problem configure a one-shot-cron-run right after condor start, I don't have the syntax for that in my head but you will find the solution in the manual ;)
>
> Last thing I think I am spotting is you need to put:
>
> STARTD_CRON_myjob_MODE = Periodic
>
> Also the startd logfile should give you some insight about the run status of your cron job ...
>
> Best
> christoph
>