Thanks, Stefan! I'll have a look at the "success stories" section of the page and check the various HPC sites to see if their site specific docs are available online as that may answer my question without me needing to pester any busy admins.
As for x2go directly on the execution nodes, that doesn't work so well in the HPC environment. I provided the example of double ssh just to illustrate that I'd ruled out the submission of an interactive session under PBS Professional was not contributing to the problem. When folks work on the execution nodes, it needs to be via a job submitted with qsub, which is either a script that can be left unattended or an interactive session that can have X11 forwarding enabled. Without going through qsub, there is no way to track nor limit the resource use based on the requests (for example mem=20gb,ncpus=4). Cheers, Scott p.s. Apologies for the double reply. I missed the list on my first ________________________________ From: x2go-user <x2go-user-boun...@lists.x2go.org> on behalf of Stefan Baur <x2go-m...@baur-itcs.de> Sent: Wednesday, 23 September 2020 6:13 PM To: x2go-user@lists.x2go.org <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] Lag in RStudio desktop in nested ssh sessions (or qsub -I) MacOS clients Am 22.09.20 um 23:40 schrieb Scott Wood: > Hi folks, > > Multi-layered one here. We have x2goserver > (4.1.0.4-0.0x2go1.0.git20200228.1815.heuler.el7) available on a (CentOS7) > login node of our HPC cluster for folks to submit jobs from. If they start > an x2go client session from a Mac to our login node, submit interactive jobs > with X11 tunnelling enabled (or even just ssh -X directly to an execution > node) and run RStudio (1.1.463) desktop from within that second host, there > is an un-usable lag in their session. If they type in the console, it can > take up to 10 seconds to register and display the keystroke. No errors, > everything works, it just isn't very responsive. Linux x2go clients are fine. > Windows x2go clients are fine. > > I know that's a lot of layers they're going through but I'm at a loss for > identifying which layer is the issue. Any troubleshooting tips? Anyone out > there experiencing similar symptoms? Well, we do have several HPC cluster operators that use X2Go - see our "success stories" list in the Wiki. Maybe it would make sense to contact them directly and see if they've had the same issue? Also, why can't you run X2GoServer directly on the execution nodes, instead of using ssh -X? If the login node is the only one with a publicly accessible IP, that's not a problem - Activate the proxy feature in the X2GoClient session setup and tell X2GoClient to use your login node as an SSH proxy (i.e. "jump host"). Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 _______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
_______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user