Most information here is OBSOLETE as of 2018 Oct 17

Computer Restart Procedures

Here is where we should keep information on how to restart the computers that periodically need restarting.

• Useful links

Which models run on which machines?

• Answer: Electronics/Existing RCG DCUID and gds ids

• c1sus

This machine runs the c1x02, c1sus, c1mcs, c1rms FE models. It controls the BS, ITMX, ITMY, PRM,SRM,MC1,MC2, and MC3 optics.

On reboot, these models should automatically start up. See also the fb/DAQ section.

• c1ioo

This machine runs the c1x03, c1ioo, and c1gpt FE models. It controls mode cleaner wavefront sensors, mode cleaner length, and green locking.

On reboot, these models should automatically start up. See also the fb/DAQ section.

c1ioo is a Sun X4600 machine. As such for a complete shutdown (not normally necessary but sometimes), do the following:

Shutdown the computer normally. (Power button or "shutdown -h now").

Go out to the rack and unplug all 4 power supply cables on the back of the machine.

Wait for a bit for the machine to completely stop (30 seconds or so).

Plug all the cables back in, and press the power button.

• fb and DAQ issues

For dataviewer to get data you need to make sure "daqd" and "nds pipe" are running on the fb machine.

• If they are not running, you can start by hand by doing:
• 1. ssh fb
• 2. screen

• 3. /opt/rtcds/caltech/c1/target/fb/daqd -c ./daqdrc &

• 4. /opt/rtcds/caltech/c1/target/fb/nds pipe > nds.log &

• 5. Press ctrl-a and then ctrl-d.
• Eventually there should be a script to automatically restart these if they go down

For testpoints to be available for a given front end, you need running on the correct front end computer:

• The IOP needs to be running, since it handles, it is genamed something like c1x00, c1x01, etc.
• "sudo /opt/rtcds/caltech/c1/scripts/startc1SYSNAME" where SYSNAME is something like sus or ioo or x02
• The above starts the IOCs, awgtpman, and loads the front end module.
• mx_streams running (use "sudo /etc/restart_streams") this should start a mx_stream for each front end system and is needed to talk to the fb

To confirm the necessary codes are running on a front end, you can:

• To check if the front ends are loaded, you can use "lsmod" on the front end machine, looking for c1SYSNAMEfe entries
• To check if the IOCs are running, you can "ps -ef | grep epicsC1.cmd" - there should be 1 per model
• To check if mx_streams are running, you can "ps -ef | grep mx_stream" - there should be 1 per model
• To check if awgtpman are running, you can "ps -ef | grep awgtpman" - there should be 1 per model

Cold start order is:

• 0. If necessary, stop everything (fb, front ends, mx_streams, etc)
• 1. Start fb codes (daqd, nds)
• 2. Start IOP (startc1x##)
• 3. Start FE models (startc1SYSNAME)
• 4. Start mx_streams (/etc/restart_streams)
• If the DAQ is in a bad state, try to start fresh in this order. It seems to usually work.

• nodus

Nodus is a Solaris box in the rack in the office. Here are some of the things that it runs that you will want to restart:

• EPICS_gateway

• ndsproxy

• Apache (Required for SVN remote access)

• elog