You can run the qrsh tight integration with SSH, just alter the
rsh_command and rsh_daemon configuration variables.
I don't remember where I read this (probably the official
documentation), but here's the relevant section of my "qconf -mconf":
qlogin_command /opt/sge/util/resources/wrappers/qlogin_wrapper
qlogin_daemon /opt/sge/util/resources/wrappers/rshd-wrapper
rlogin_command /usr/bin/ssh -X
rlogin_daemon /opt/sge/util/resources/wrappers/rshd-wrapper
rsh_command /usr/bin/ssh -X
rsh_daemon /opt/sge/util/resources/wrappers/rshd-wrapper
For the commands, "-X" is used to have X forwarding, so that the users
can use X applications heavy on the CPU on the nodes.
You'll need to have passphrase-less authentication for all your users.
So "ssh node-01" for users opens a shell without manual intervention.
The connection uses a randomly-selected port, so you'll need a relaxed
firewall on the nodes. This is because a different SSH daemon is started
for each connection. The tight integration needs this so that all
processes are children of the shepherd process and can be tracked.
Raymond Norris @ 2017-02-17 17:54:46:
> Hi,
>
> I'm using SoGE 8.1.9.
>
> When we setup our jobs to run with loose integration and SSH, things work
> fine. I'm now trying to configure this with tight integration and qrsh.
> Sans a dozen or so ports, everything's closed. My understanding is that qrsh
> uses rsh underneath and that we need to open port 514, which we've done.
> However, we get the following:
>
> qrsh -inherit -verbose node-01 smpd -s -phrase ... -port ...
> Starting server daemon at host "node-01"
> error: executing task of job 1032 failed: failed sending task to
> execd@node-01: got send error
> error: commlib error: got select error (No route to host)
>
> To me, that tells me we don't have 514 open ("No route to host"). Also, I
> think the issue is that we're not running rshd on node-01, which I'm not sure
> if they're ok with running - which we'd need to, righ? So my question is,
> how do I get qrsh working so that I can track resources, but configure it
> with SSH - or can this not work - do I need to rsh?
>
> I'm assuming there are other sites in the same situation - want to use tight
> integration but aren't comfortable supporting rsh.
>
> Thanks,
> Raymond
>
> _______________________________________________
> SGE-discuss mailing list
> SGE-discuss@liv.ac.uk
> https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
_______________________________________________
SGE-discuss mailing list
SGE-discuss@liv.ac.uk
https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
