Re: [HTCondor-users] Dedicated Scheduler Jobs' PATH prefixed by /usr/bin?

[Carsten Aulbert <carsten.aulbert@xxxxxxxxxx>]

Hi Thomas,

On 12/2/25 14:48, Thomas Hartmann wrote:
> quick question, but on the submission side there is no
>  Â getenv
> set, or? I.e., have Condor copy all the submission shell envs to the job 
> (which could lead to some odd behavior like the one you are describing)

not in this (kind of) minimal not-working example.

The user in question does use getenv = True and has a ton of things in 
PATH from a local spack installation tree.

The problem manifested itself as it ran the wrong python binary, it 
should come from spack but with the prefixed /usr/bin it of course took 
the OS version.

The weird thing is, submitting the almost same submit file (only with 
universe changed from 11 to 5) into our main pool without a dedicated 
scheduler yields

PATH=/invalid/path:/usr/local/bin:/usr/bin:/bin

as the output of /usr/bin/env

I'm currently trying to figure out with condor_config_cal -summary 
whether there is something massively different between the submit and 
execute points involved, but so far I'm drawing blanks.

Cheers

Carsten
--
Dr. Carsten Aulbert, Max Planck Institute for Gravitational Physics,
CallinstraÃe 38, 30167 Hannover, Germany, Phone +49 511 762 17185

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature