> Hi, > > > Am 17.02.2017 um 18:54 schrieb Raymond Norris > <raymond.nor...@mathworks.com>: > > > > 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: > > No. If you set: > > $ qconf -mconf > … > rsh_command builtin > rsh_daemon builtin > > it uses its own protocol. Even when set to `rsh` resp. `rshd`, it will in > both > cases use a random port, not 514. > > https://arc.liv.ac.uk/SGE/htmlman/htmlman5/remote_startup.html might > give some insight. > > > > qrsh -inherit -verbose node-01 smpd -s -phrase ... -port ... > > This looks like an old startup of MPICH2. You don't use Hydra?
We ship MPICH2 with our application, so I'm starting there. I've built it with Hydra, but it fails. I'm guessing, as Simao Afonso references, each ssh connection requires a different ephemeral 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? > > See the above provided link, `ssh` is also covered near the end of the > document. I can test the PAM, but in the end, will I be in the same situation where ssh/sshd will use an array of ports? As it stands now, keeping most of the ports closed, these are my options 1. loose integration with SSH: works 2. tight integration with Hydra: fails -- needs ephemeral ports 3. tight integration with qrsh: fails -- needs ephemeral ports 4. tight integration with qrsh, using SSH: not tested yet (needs ephemeral ports?) 5. recompile SoGE w/ tight SSH Am I overlooking any other options? > > I'm assuming there are other sites in the same situation - want to use tight > integration but aren't comfortable supporting rsh. > > Inside a cluster this is most likely not a problem. Usually the login server > is > hard to the outside (we even allow only login by ssh-keys), but inside there > is > nothing on the nodes which isn't on the login server. And any `sshd` or `rshd` > is running on the nodes only anyway, not the login machine. > > -- Reuti > > > > Thanks, > > Raymond _______________________________________________ SGE-discuss mailing list SGE-discuss@liv.ac.uk https://arc.liv.ac.uk/mailman/listinfo/sge-discuss