Hi Daniel,
Our LTS series tends not to contain major changes because it is intended for bug fixes only. Doing some git archeology, there were not that many changes that effected the Startd/Starter daemons, so I am unsure why this is happening. Is that configuration for
the desktop policy fully custom or built off of one of the configuration templates. The output of
condor_config_val -summary could be helpful here.
-Cole Bollig
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Daniel Brückner <daniel.brueckner@xxxxxxxxxxxxxxxxxx>
Sent: Monday, September 9, 2024 2:19 AM To: HTCondor-Users Mail List <HTCondor-users@xxxxxxxxxxx> Subject: [HTCondor-users] Jobs are starting even in Owner State after updating to 23.0.14 Hi there,
After updating my nodes to "23.0.14 2024-08-07" my Start _expression_ is ignored and jobs are starting in Owner-State. ##### root@cm:~# condor_status pc40 Name OpSys Arch State Activity LoadAv Mem ActvtyTime slot1@pc40 LINUX X86_64 Owner Idle 0.000 1746 0+00:00:00 slot1_1@pc40 LINUX X86_64 Claimed Busy 0.000 65536 0+00:00:00 slot1_2@pc40 LINUX X86_64 Claimed Busy 0.000 4096 0+00:00:00 slot1_3@pc40 LINUX X86_64 Claimed Busy 0.000 4096 0+00:00:00 slot1_4@pc40 LINUX X86_64 Claimed Busy 0.000 4096 0+00:00:00 ##### After downgrading to "23.0.12 2024-06-13" everting works as aspected and jobs are starting when the node is in "unclaimed" state only. Are there any major changes in 23.0.14? Here's my configuration: ##### KeyboardBusy = KeyboardIdle < $(StartIdleTime) CPUIdle = $(NonCondorLoadAvg) <= $(BackgroundLoad) CPUBusy = $(NonCondorLoadAvg) >= $(HighLoad) KeyboardNotBusy = ($(KeyboardBusy) == False) START = ($(CPUIdle) || $(KeyboardNotBusy)) IS_OWNER = ($(CpuBusy) || $(KeyboardBusy)) #### condor_drain is working and will evict all running jobs. Do you have any idea what's going on there? Best regards and thanks for your support, Daniel _______________________________________________ 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/ |