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: 10585     Entry time: Wed Oct 8 15:31:31 2014     In reply to: 10011
Author: Jenne 
Type: Update 
Category: CDS 
Subject: Computer status 

After the Great Computer Meltdown of 2014, we forgot about poor c0rga, which is why the RGA hasn't been recording scans for the past several months (as Steve noted in elog 10548).

Q helped me remember how to fix it.  We added 3 lines to its /etc/fstab file, so that it knows to mount from Chiara and not Linux1.  We changed the resolv.conf file, and Q made some simlinks.

Steve and I ran ..../scripts/RGA/RGAset.py on c0rga to setup the RGA's settings after the power outage, and we're checking to make sure that the RGA will run right now, then we'll set it back to the usual daily 4am run via cron.

EDIT, JCD:  Ran ..../scripts/RGA/RGAlogger.py, saw that it works and logs data again.  Also, c0rga had a slightly off time, so I ran sudo ntpdate -b -s -u pool.ntp.org, and that fixed it.

Quote:

 

In all of the fstabs, we're using chiara's IP instead of name, so that if the nameserver part isn't working, we can still get the NFS mounts.

On control room computers, we mount the NFS through /etc/fstab having lines like:

192.168.113.104:/home/cds /cvs/cds nfs rw,bg 0 0
fb:/frames /frames nfs ro,bg 0 0

Then, things like /cvs/cds/foo are locally symlinked to /opt/foo

For the diskless machines, we edited the files in /diskless/root. On FB, /diskless/root/etc/fstab becomes

master:/diskless/root                   /         nfs     sync,hard,intr,rw,nolock,rsize=8192,wsize=8192    0 0
master:/usr                             /usr      nfs     sync,hard,intr,ro,nolock,rsize=8192,wsize=8192    0 0
master:/home                            /home     nfs     sync,hard,intr,rw,nolock,rsize=8192,wsize=8192    0 0
none                                    /proc     proc    defaults          0 0
none                                    /var/log        tmpfs   size=100m,rw    0 0
none                                    /var/lib/init.d tmpfs   size=100m,rw    0 0
none                                    /dev/pts        devpts  rw,nosuid,noexec,relatime,gid=5,mode=620        0 0
none                                    /sys            sysfs   defaults        0 0
master:/opt                             /opt      nfs    async,hard,intr,rw,nolock  0 0
192.168.113.104:/home/cds/rtcds         /opt/rtcds      nfs     nolock  0 0
192.168.113.104:/home/cds/rtapps        /opt/rtapps     nfs     nolock  0 0

("master" is defined in /diskless/root/etc/hosts to be 192.168.113.202, which is fb's IP)

and /diskless/root/etc/resolv.conf becomes:

search martian

nameserver 192.168.113.104 #Chiara

 

 

 

ELOG V3.1.3-