> Am 29.05.2017 um 16:08 schrieb [email protected]: > > Out of the blue, qrsh refuses to work. It will not allow me to connect to any > node, but ssh works fine from all nodes to all nodes. ??? > > [jjimene@med-login2 bin]$ qrsh -verbose > Your job 4909901 ("QRLOGIN") has been submitted > waiting for interactive job to be scheduled ... > Your interactive job 4909901 has been successfully scheduled. > Establishing /usr/bin/ssh -Y -A session to host med0241 ... > ssh_exchange_identification: read: Connection reset by peer > /usr/bin/ssh -Y -A exited with exit code 255
So, you are using SSH and not the built-in communication. How is the authentication set up – hostbased or ssh-keys? Was any of the packages updated on either side? > [jjimene@med-login2 bin]$ ssh med0241 > Last login: Mon May 29 15:53:20 2017 from med-qmaster.mdc-berlin.net > > What could be causing this? Any firewall in place? The SSH login by SGE will use a random port, not necessarily 22. -- Reuti > Again, the fact that qrsh does not make any effort to tell me where the error > is coming from is making debugging this harder than necessary. How can I tell > qrsh to pass -vvvv to the ssh call and give me access to the resulting log? > > Mfg, > Juan Jimenez > System Administrator, HPC > MDC Berlin / IT-Dept. > Tel.: +49 30 9406 2800 > _______________________________________________ > SGE-discuss mailing list > [email protected] > https://arc.liv.ac.uk/mailman/listinfo/sge-discuss > _______________________________________________ SGE-discuss mailing list [email protected] https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
