As an alternative to X11 Forwarding, using VNC to access the cluster is another way to run graphically intensive applications.
On the clusters, we have web dashboards set up that can run VNC for you as a job and forward your session back to you via your browser using Open OnDemand. To use the Remote Desktop tab, browse under the "interactive apps" drop-down menu item.
We strongly encourage using Open OnDemand unless you have specific requirements otherwise.
Setup vncserver on a Cluster
Connect to the cluster with X11 forwarding enabled. If on Linux or Mac,
ssh -Y netid@cluster, or if on Windows, follow our X11 forwarding guide.
Start an interactive job on cluster with the
--x11flag (see Slurm for more information). For this description, we’ll assume you were given node c04n03:
srun --pty --x11 -p interactive bash
- On that node, run the VNCserver. You’ll see something like:
c04n03$ vncserver New 'c31n02.grace.hpc.yale.internal:1 (kln26)' desktop is c31n02.grace.hpc.yale.internal:1 Creating default startup script /home/fas/hpcprog/kln26/.vnc/xstartup Starting applications specified in /home/fas/hpcprog/kln26/.vnc/xstartup Log file is /home/fas/hpcprog/kln26/.vnc/c31n02.grace.hpc.yale.internal:1.log
The :1 means that your DISPLAY is :1. You’ll need that later, so note it. The first time you run "vncserver", you’ll also be asked to select a password for allowing access.
On MacOS, if connecting with TurboVNC throws a security exception such as "javax.net.ssl.SSLHandshakeException", try adding the SecurityTypes option when starting vncserver on the cluster:
vncserver -SecurityTypes VNC,OTP,UnixLogin,None
Connect from your local machine (laptop/desktop)
From a shell on your local machine, run the following ssh command:
ssh -Y -L7777:c04n03:5901 YourNetID@cluster_login_node
This will set up a tunnel from your local port 7777 to port 5901 on c04n03. You will need to customize this command to your situation. The 5901 is for display :1. In general, you should put 5900+DISPLAY. The 7777 is arbitrary; any number above 3000 will likely work. You’ll need the number you chose for the next step.
On your local machine, start the vncviewer application. Depending on your local operating system, you may need to install this. We recommend TurboVNC for Mac.
When you start the viewer, you’ll need to tell it which host and port to attach to. You want to specify the local end of the tunnel. In the above case, that would be localhost::7777. Exactly how you specify this will depend a bit on which viewer you use. E.g:
You should be prompted for the password you set when you started the server.
Now you are in a GUI environment and can run IGV or any other rich GUI application.
In MobaXterm, create a new Session (available in the menu bar) and then select the VNC session.
To fill out the VNC Session setup, click the "Network settings" tab and check the box for "Connect through SSH gateway (jump host). Then fill out the boxes as follows:
- Remote hostname or IP Address: name of the node running your VNC server (e.g. c01n01)
- Port: 5900 + the
DISPLAYnumber from above (e.g. 5901 for
DISPLAY = 1)
- Gateway SSH server: ssh address of the cluster (e.g. grace.hpc.yale.edu)
- Port: 22 (should be default)
- User: netid
- Use private key: check this box and click to point to your private key file you use to connect to the cluster
When you are done, click OK. If promoted for a password for "localhost", provide the vncserver password you specified in the previous step.
If the VNC server looks very pixelated and your mouse movements seem laggy, try clicking the "Toggle scaling" button at the top of the VNC window.
When you are all finished, you can kill the vncserver by doing this in the same shell you used to start it (replace :1 by your display number):
vncserver -kill :1