Getting Started - Connecting

From Xem2
Jump to navigationJump to search

Overview

Users can access the JLab Common Users Environment (CUE) by tunneling through the login1 or login2 server at JLab.
ssh -t -L6437:localhost:5912 cmorean@login2.jlab.org ssh -t -L5912:localhost:5912 <destination_computer>

  • The red are already in use and you should CHANGE to a different port for your use. (Refer to the list below to see which ports are already in use).
  • It is common to connect to chislobog (XEM only), ifarm, or jlabl1 - jlabl3.
  • In order to use a vncserver, you will need to use a computer other than an ifarm computer.
    • Highly recommended over x11 port forwarding because of connection speed requirements
    • You can check your connection speed to JLab is not the problem by using JLab's SpeedTest.

Issues with WSL

The initial WSL (windows subsystem for linux) LANG is not set properly for JLab. You will need to edit /etc/default/locale to
LANG=en_US.UTF8
If this is not set properly, you will be unable to open a terminal window in a vnc session. You will also get a few perl issues upon logging into JLab above the title screen.

Used Numbers

Once you use a number note it on this list. Update this list or contact someone who can.

Chislobog Ports In Use
Port Number User
07 Nadia
11 Ryan
12 Casey
16 unknown

VNC Server Setup

  1. Insure VNC Viewer is installed on your computer.
  2. Start the VNC viewer process on <destination_computer>. vncserver -geometry 1920x1080 :12
  3. Open the VNC application on your computer.
    • Click file --> New connection... --> A new window should pop up
    • For IP address or host name use localhost:6437
    • Name this VNC connection anything you will remember and click Okay
  4. Other Useful VNC Commands
    • To kill a VNC server on <destination_computer> vncserver -kill :12
    • To set a new VNC password vncpasswd
    • To edit the VNC window render resolution, change the numbers in blue for the command vncserver -geometry 1920x1080 :12
  • The 12 should be the same number as you chose in the previous section.

Using PuTTY to SSH

  • Currently not recommended, but possible with the right configuration.

Common Connection Issues

  • Tunneling Problems
    • Conflicting or incorrect SSH keys in known_hosts
  • VNC Server Problems
    • If you tunnel and only specifying login.jlab.org, the machine will choose either one or the other, which sometimes breaks vncservers for UNKNOWN REASONS.
    • VNC Servers should be started on the port highlighted in red using the command <vncserver -geometry 1920x1080 :<port_number>
    • VNC Servers started on different destination_computer are not accessible if you login later to some other destination_computer.
    • The computer was restarted, so the vncserver was shut down.
  • JLab /group/ /work/ /volatile/ Directories Missing (Hanging)
    • Sometimes work on connection gateways will break Lustre file system connections that are not tier-1
    • Improper JLab farm node use can cause the Lustre file system to hang. Report an incident report using the Incident Report Utility