- Do really want your job to deal with scripting to use scp and passing
around credentials? I think usually it is better/easier/safer to use
HTCondor's file transfer mechanism (which is scheduled) to move files
from your submit machine to the execute machine
I use Condor to spawn JupyterLab servers on remote machines. So my goal is to enable actual human users to run ssh, scp and condor_ssh_to_job on their JupyterLab servers.
- If you need to use scp etc, the most common reason I've encountered
for an exit status of 255 in scripts that run outside of my home
environment is because I am contacting a host not in my
$HOME/.ssh/known_hosts file (almost certainly not the case if you are
using HTCondor without a shared file system or across administrative
domains). To remedy, consider passing command-line switches to scp/ssh
scp -o UserKnownHostsFile=./my_temporary_known_host ssh_host ...
$HOME/.ssh/know_hosts is definitely available.
Could this problem be somehow related to TTY?
Here are the results of a recent test:
Job description file:
universe = vanilla