> Am 29.05.2017 um 18:00 schrieb juanesteban.jime...@mdc-berlin.de: > > On 29.05.17, 17:56, "Reuti" <re...@staff.uni-marburg.de> wrote: > > >> Am 29.05.2017 um 17:26 schrieb juanesteban.jime...@mdc-berlin.de: >> >> I am getting this very specific error: >> >> debug1: ssh_exchange_identification: /usr/sbin/sshd: error while loading >> shared libraries: libselinux.so.1: failed to map segment from shared object > >> I don't have a specific idea as this seems to be a permission problem. Are >> you running selinux and could disable it? > > SELINUX is disabled on all nodes.
Ok. > >> However, ssh works fine outside of qrsh. Every single test succeeds, from >> all nodes to all nodes. > >> This is usually handled by the default running `sshd` on port 22, but the >> one started by SGE runs on a different port. > > Started where??? On the node where the qrsh will be sent, by the exec daemon? It's the shepherd who will start it. > That’s a heck of a big clue! Is there a way to disable this and use the > existing sshd? Not in the default setting. sgeadmin root /usr/sge/bin/lx24-em64t/sge_execd sgeadmin root \_ sge_shepherd-224557 -bg root root \_ sshd: reuti [priv] reuti reuti \_ sshd: reuti@pts/0 reuti reuti \_ -bash reuti reuti \_ ps -e f -o user,ruser,command This is completely unrelated to the default `sshd` to log in on port 22. In the standard configuration it will use the same config files though. == You could try to use wrappers for both entries and ignore the port, but then you will lose job control and accounting (I have no clue whether this will work). The detailed startup is explained here: https://arc.liv.ac.uk/SGE/htmlman/htmlman5/remote_startup.html -- Reuti _______________________________________________ SGE-discuss mailing list SGE-discuss@liv.ac.uk https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
