[A1n_d2n] [EXTERNAL] VNC server issues on the ifarm nodes

[Brad Sawatzky]

Sounds like a few of you have hit this problem trying to get a VNC
server running with a working window manager / desktop environment.

I looks like the ifarm nodes are missing some of the needed software
packages.  I'm not sure when that broke..

The simplest thing to do is run the vncserver on one of the jlablX
machines.  I've updated the 'd2n VNC Session' wiki page with a note
to that effect.  Once you have a working session, then just open a
terminal(s) and ssh into ifarm180x as you normally would.

If you do your usual thing to run a vncserver on jlablX and still don't
get a working desktop, try this and see if it solves your problem.
  https://hallaweb.jlab.org/wiki/index.php/How_to_connect_to_a_d2n_VNC_Session#Configure_the_VNC_Server

If you have 'dangling' vnc servers running on ifarm180x (or elsewhere),
do kill them so they don't sit idle and occupy slots.  You can see what
might be still running by:
  % ls $HOME/.vnc/*.pid
  .vnc/ifarm1802:14.pid
  .vnc/ifarm1802:44.pid
If I know those aren't working sessions, I can log into ifarm1802 and
run the following to clean up (for example).
  % vncserver -kill :14
  % vncserver -kill :44
(Don't worry if the 'kill' command complains, sometimes those files are
old/obsolete.  You can't cause any problems by running the command.)

-- Brad

-- 
Brad Sawatzky, PhD <brads at jlab.org>  -<>-  Jefferson Lab / Hall C / C111
Ph: 757-269-5947  -<>-  Fax: 757-269-5235  -<>- Pager: brads-page at jlab.org
The most exciting phrase to hear in science, the one that heralds new
  discoveries, is not "Eureka!" but "That's funny..."   -- Isaac Asimov