The UMUI on PUMA cannot establish an SSH link to the lander on MONSooN

[till]

Currently I
cannot submit jobs to MONSooN from PUMA (through the UMUI) since I get an
authentication failure. I have already re-setup all the necessary steps following
http://cms.ncas.ac.uk/wiki/MonsoonSshAgent
but to no avail unfortunately.

Robin Smith has the same problem. Probably this is a consequence of the hardware failure of the lander and the subsequent loss of all data on it?

NB if I ssh directly from a shell on PUMA it works!

[till]

Robin and I found out what was wrong! It was my ssh setup on the lander. Problem solved!

However, I now always have to manually log in to the ibm02 from the lander. This is just a minor nuisance. Before, I used to have something in my bashrc on the lander that forwarded me automatically to the ibm, but would not get in the way of the UMUI. What would it have been?

[ros]

Hi Till,

I've come across one way of being automatically forward from lander to the ibm should you still want/need this. I've not tested it with the UMUI but don't think it will interfere.

Add the following to $HOME/.bash_profile (think it needs to be .bash_profile rather than $HOME/.profile).

# Automatically go to ibm02/postproc as required
autofile=$HOME/.autologin

if [ -s ${autofile} ]
then 
  echo "Automatically logging to system defined by ${autofile} – remove this file if you want to stay on Lander"

  ssh -Y $(cat ${autofile})
fi

The idea being, you have $HOME/.autologin on lander containing the string ‘ibm02’ or ‘postproc’ to set default destination, or just delete the file (or have a non-existent destination) and you’ll stop at lander. (You should be able to alter file contents remotely with sftp and rm, or just scp a null file in to overwrite the previous version.

Cheers,
Ros.