40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  PSL  Not logged in ELOG logo
Entry  Thu Sep 7 18:21:56 2017, awade, Craig, DailyProgress, Computers, Acromag2 down 2017-09-07_17.22.30.jpg2017-09-07_17.19.41.jpg2017-09-07_17.19.19.jpg
    Reply  Thu Sep 7 21:47:39 2017, awade, DailyProgress, Computers, New computer rebuild ws3 up 
       Reply  Mon Sep 11 21:02:46 2017, awade, DailyProgress, Computers, ws3: fixing ligo cds tools and moving IP address 
Message ID: 1911     Entry time: Mon Sep 11 21:02:46 2017     In reply to: 1901
Author: awade 
Type: DailyProgress 
Category: Computers 
Subject: ws3: fixing ligo cds tools and moving IP address 

For some reason medm and striptool were unable to access channels on ws3.  At the time I built the computer last week I didn't test any of the LIGO tools.  

After a bit of fiddling with the network settings we moved ws3 back from to and we were able to access channels again. It is not clear exactly why this worked.  We should debug it, but we'll leave it for now.


Before we found the IP address fix I purged all the ligo cds tools, updated apt-get and installed again. This time around I was able to install the cds-workstation package.

Jamie et al have a standard install with a couple of lines for all the ligo cds tools: https://git.ligo.org/cds-packaging/docs/wikis/home. These were the instructions I followed, last week it was throwing a bunch of errors about not being able to retrieve things.

I activated superuser and purged all the ligo related packages out of the system with

apt-get purge lscsoft-archive-keyring cds-unstable-archive-keyring etc

I then ran 

apt-get update

apt-get -y --force-yes install lscsoft-archive-keyring cds-unstable-archive-keyring

apt-get update

The packages were then re downloaded and up to date.  After that I ran 

apt-get install cds-workstation

which actually worked this time (first). A blue screen popped up asking me about kerbose servers or something. I just left it blank and hit enter, hopefully this is ok.

All good for now although the mystery IP issue is unresolved.

ELOG V3.1.3-