On Tue, Feb 27, 2018 at 10:46:57AM +0100, Reuti wrote: > Hi Nils: > > > Am 27.02.2018 um 10:11 schrieb Nils Giordano <[email protected]>: > > however you were right: `ssh` is definitively used to access nodes > > (probably on purpose since we have access to several GUI apps). Your > > answer made me check my ~/.ssh/ directory, and I found dozens of > > *.socket files in there. > > > > After removing these files, qmake and qrsh perform flawlessly (shepherd > > exit code 0).
> > I still do not know what caused this problem and at which > > point these files were created, but I will know what to look for would > > this problem reappear. > > For me I never saw any socket files created in my ~/.ssh Maybe it's custom > with your other graphical apps. I wonder if the ssh_config has ControlMaster set? That apparently creates a socket to allow multiple ssh commands to share a single connection. I suspect it would run into problems with grid engine tight integration and might also have issues when the directory is on a shared filesystem. If this is the root cause then setting 'ControlMaster no' in ~/.ssh/config should prevent a reoccurrencei for you personally. Qmake is probably affected more than most parallel libraries because most parallel libraries execute a single qrsh and then fork on the remote side while I suspect (I haven't checked) that qmake launches one qrsh per process. If this is the case then I would suggest contacting the cluster admin and requesting they disable ControlMaster for the ssh launched by qrsh. Assuming a fairly normal linux box you should be able to check the setting with: grep -i controlmaster /etc/ssh/ssh_config William
signature.asc
Description: PGP signature
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
