Christoph The runscript uses only absolute paths. We just got a new version of this code where I get this problem with the new version, and not with the old version. I check ldd for the binaries of both versions and get the same result. Have discussed with supplier of the cfd code and the didnât have any good suggestions yet. P From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of Beyer, Christoph Hi, make sure all the paths you need are set in the bash script or use absolute paths if in doubt. The interactive login uses ssh mechanisms and therefore sources your
environment which is not necessarily the case in a regular condor job. Try ldd <binary> to check if the libraries the binary uses are hidden somewhere and put all these paths in your bash script (LD_LIBRARY_PATH etc) ... best christoph
Von:
"Peter Ellevseth" <Peter.Ellevseth@xxxxxxxxxx> Jason We have a shared file system between all nodes. When I run condor_submit -interactive I get a shell in the same folder as I was previously, but from the âviewâ of the execute node. I can then execute simply by
â./runscriptâ. Yes, I get the normal log/out/error files. I have checked the env and there is nothing there that tells me why the job wonât start. I can also ssh to one of my startd machines and start the job manually with the runscript. Loss of ideas here now. P From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of Jason Patton Hi Peter, You say that when you submit an interactive job, you run the script by doing "./runscript". Do your jobs ever use condor file transfer or is your pool set up to assume a shared file system? When you submit the job normally, do you still get back the output (stdout) and error (stderr) files? It might be useful to print out the environment at the very beginning of the script and compare between a normal
job and an interactive job. Jason Patton On Mon, May 3, 2021 at 5:04 PM Peter Ellevseth <Peter.Ellevseth@xxxxxxxxxx>
wrote:
|