40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Mon Jun 9 11:42:00 2014, Jenne, Update, CDS, Computer status 
    Reply  Mon Jun 9 12:19:17 2014, ericq, Update, CDS, Computer status 
       Reply  Mon Jun 9 22:26:44 2014, rana, zach, Update, CDS, SLOW controls recovery 
          Reply  Wed Jun 11 14:36:57 2014, Jenne, Update, CDS, SLOW controls recovery 
             Reply  Wed Jun 11 15:57:18 2014, Jenne, Update, CDS, Note on cables for talking to slow computers 06111401.PDF
                Reply  Thu Jun 12 15:31:47 2014, Jamie, Update, CDS, Note on cables for talking to slow computers 
             Reply  Wed Jun 11 16:01:31 2014, Steve, Update, CDS, c1Vac1 and c1vac2 rebooted beforeReboot.png
                Reply  Fri Oct 10 14:27:44 2014, Steve, Update, CDS, c1Vac1 and c1vac2 reboot was a failure c1vac1resetReboot.pngc1Vac1&2down.jpg
       Reply  Wed Oct 8 15:31:31 2014, Jenne, Update, CDS, Computer status 
    Reply  Mon Jun 9 22:40:36 2014, Jenne, Update, CDS, Fast front end computers up 
    Reply  Tue Jun 10 09:25:29 2014, Jamie, Update, CDS, Computer status: should not be changing names 
Message ID: 10010     Entry time: Mon Jun 9 11:42:00 2014     Reply to this: 10011   10016   10018
Author: Jenne 
Type: Update 
Category: CDS 
Subject: Computer status 

Current computer status:

All fast machines except c1iscey are up and running. I can't ssh to c1iscey, so I'll need to go down to the end station and have a look-see. On the c1lsc machine, neither the c1oaf nor the c1cal models are running (but for the oaf model, we know that this is because we need to revert the blrms block changes to some earlier version, see Jamie's elog 9911).

Daqd process is running on framebuilder.  However, when I try to open dataviewer, I get the popup error saying "Can't connect to rb", as well as an error in the terminal window that said something like "Error getting chan info".

Slow machines c1psl, c1auxex and c1auxey are not running (can't telnet to them, and white boxes on related medm screens for slow channels).  All other slow machines seem to be running, however nothing has been done to them to point them at the new location of the shared hard drive, so their status isn't ready to green-light yet.

Things that we did on Friday for the fast machines:

The shared hard drive is "physically" on Chiara, at /home/cds/.  Links are in place so that it looks like it's at the same place that it used to be:  /opt/rtcds/...... 

The first nameserver on all of the workstation machines inside of the file /etc/resolv.conf has been changed to be, which is Chiara's IP address (it used to be, which was linux1).  This change has also been made on the framebuilder, and in the framebuilder's /diskless/root/etc/resolv.conf file, which is what all of the fast front ends look to. 

On the framebuilder, and in the /diskless place for the fast front ends, presumably we must have changed something to point at the new location for the shared drive, but I don't remember how we did that [ERIC, what did we do???]

The slow front ends that we have tried changing have not worked out. 

First, we tried plugging a keyboard and monitor into c1auxey.  When we key the crate to reboot the machine, we get some error message about a "disk A drive error", but then it goes on to prompt pushing F1 for something, and F2 for entering setup.  No matter what we press, nothing happens.  c1auxey is still not running.

We were able to telnet into c1auxex, c1psl, and c1iool0.  On each of those machines, at the prompt, we used the command "bootChange".  This initially gives us a series of:

$ telnet c1susaux
Connected to c1susaux.
Escape character is '^]'.

c1susaux > bootChange

'.' = clear field;  '-' = go to previous field;  ^D = quit

boot device          : ei
processor number     : 0
host name            : linux1
file name            : /cvs/cds/vw/mv162-262-16M/vxWorks
inet on ethernet (e) :
inet on backplane (b):
host inet (h)        :
gateway inet (g)     :
user (u)             : controls
ftp password (pw) (blank = use rsh):
flags (f)            : 0x0
target name (tn)     : c1susaux
startup script (s)   : /cvs/cds/caltech/target/c1susaux/startup.cmd
other (o)            :

value = 0 = 0x0
c1susaux >

If we go through that again (it comes up line-by-line, and you must press Enter to go to the next line) and put a period a the end of the Host Name line, and the Host Inet (h) line, they will come up blank the next time around.  So, the next time you run bootChange, you can type "chiara" for the host name, and "" for the "host inet (h)".  If you run bootChange one more time, you'll see that the new things are in there, so that's good.

However, when we then try to reboot the computer, I think the machines weren't coming back after this point.  (Unfortunately, this is one of those things that I should have elogged back on Friday, since I don't remember precisely).  Certainly whatever the effect was, it wasn't what I wanted, and I left with the machines that I had tried rebooting, not running.

ELOG V3.1.3-