This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
chara:trouble_shooting [2023/02/08 19:24] charaobs [The new OPLE system] |
chara:trouble_shooting [2023/02/08 19:26] charaobs [Restarting Servers using the rc.local file] |
||
---|---|---|---|
Line 49: | Line 49: | ||
==== Restarting Servers using the rc.local file ==== | ==== Restarting Servers using the rc.local file ==== | ||
- | \\ This procedure is applicable to servers that have not switched over to the bootlaunch paradigm, which may not be any at this point. \\ \\ If a server is not running or Socket Manager reports that a server is dead, then look at the socket manager list to find out what computer the server runs on ([[: | + | \\ |
- | \\ | + | This procedure is applicable to servers that have not switched over to the bootlaunch paradigm, which may not be any at this point.\\ |
- | Log on to the relevant computer by typing the computer name (ctrscrut, ople, s1, …). If the shortcut doesn' | + | \\ |
+ | If a server is not running or Socket Manager reports that a server is dead, then look at the socket manager list to find out what computer the server runs on ([[: | ||
+ | \\ | ||
+ | Log on to the relevant computer by typing the computer name (ctrscrut, ople, s1, …). If the shortcut doesn' | ||
+ | \\ | ||
+ | Find out if the server is running by typing "ps aux | grep // | ||
+ | [ctrscrut: | ||
+ | observe 9281 0.0 0.0 61156 692 pts/3 S+ 13:58 0:00 grep pico_1\\ | ||
+ | observe 12578 0.0 0.0 24524 11212 ? S Jun16 33:14 / | ||
+ | \\ | ||
+ | If the entry for the dead server shows up in the process list, then identify the process identification number (12578 for the example above) and kill the server by typing "kill -9 // | ||
+ | \\ | ||
+ | Look up the commands to restart the server by typing "more / | ||
+ | \\ | ||
+ | #Start PICO server for PICO #1\\ | ||
+ | /bin/rm -f / | ||
+ | / | ||
+ | / | ||
+ | \\ | ||
+ | The first command removes the lock to allow the server to restart. The second command removes the name from the socket manager listing. The last command restarts the server. Note that if you are restarting the servers as observe, you will need to remove the part of the command in the rc.local file that saves information in / | ||
+ | \\ | ||
+ | There are text files on the desktop with many of the restart commands. Use these files for quick access to the relevant commands. The commands are edited and can be copied exactly as written. Files include Dome servers and all servers running on ctrscrut. Many of these commands are also located on the [[: | ||
Shutters Server | Shutters Server | ||
- | \\ The Shutters server can become unresponsive or disconnected from the Socket Manager. This server must be restarted from the lab and not from the Control Room. Follow these instructions to restart it. Note that Shutters runs on ople, not ctrscrut. \\ \\ To start the shutter server on ople: \\ \\ Log into the ople computer and kill the process labeled shutters with the PID as described in **Restarting Servers** | + | \\ |
+ | The Shutters server can become unresponsive or disconnected from the Socket Manager. This server must be restarted from the lab and not from the Control Room. Follow these instructions to restart it. Note that Shutters runs on ople, not ctrscrut.\\ | ||
+ | \\ | ||
+ | To start the shutter server on ople:\\ | ||
+ | \\ | ||
+ | Log into the ople computer and kill the process labeled shutters with the PID as described in **Restarting Servers** above.\\ | ||
+ | Turn off the power to the Shutters with the switch on the computer rack which is to the left of the computer desk and marked " | ||
+ | \\ | ||
+ | / | ||
+ | ctrscrut/ | ||
==== Restarting Socket Manager ==== | ==== Restarting Socket Manager ==== |