Re: [HTCondor-users] Issues with condor 8.8 on windows core.

[Cole Bollig <cabollig@xxxxxxxx>]

Hi Jason,

Until V10.6.0, HTCondor always renames the jobs executable to condor_exec.exe if file transfer occurs. On Windows platforms this should be further modified to copy over the correct file extension from the original executable name to the new name i.e. my_executable.bat -> condor_exec.exe - > condor_exec.bat. I assume jobs are failing at this host due to the renaming. Are all incoming jobs failing or just a subset? The StarterLogs may hold some information into the issue as it will log errors if the extension switching fails.

-Cole Bollig

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Jason Browatzke <Jason@xxxxxxxxxxxxxxxx>
Sent: Tuesday, August 13, 2024 8:00 PM
To: htcondor-users@xxxxxxxxxxx <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] Issues with condor 8.8 on windows core.

 

I am having an issue with 4 stations all running windows core server, during the transfer of jobs the condor_exec file is being created as condor_exec.exe but the content of the file is a batch file. I have other nodes with the exact same condor config file running win 11 that do not experience this and the file is named condor_exec.bat. The only difference is the OS of the host.