The CHARA Array Wiki

User Tools

Site Tools

Trace:
chara:trouble_shooting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
chara:trouble_shooting [2021/11/09 15:10]
gail_stargazer 		chara:trouble_shooting [2021/11/09 15:18]
gail_stargazer removed
Line 186: Line 186:
 ==== E1 Hut and Cooler Communications Recovery ==== ==== E1 Hut and Cooler Communications Recovery ====
  
-====   E1 HuT and Cooler Communications Recovery   \\  \\  S2 Acquisition Server Restart  ====+==== E1 HuT and Cooler Communications Recovery \\ \\ S2 Acquisition Server Restart ====
  
 S2's acquisition server resides on "S2pi4" computer. Logging on to it (ssh s2pi4) and running bootlaunch will restart it S2's acquisition server resides on "S2pi4" computer. Logging on to it (ssh s2pi4) and running bootlaunch will restart it
Line 326: Line 326:
 The most common cause for getting multiple copies of a server is using the socket manage RESTART button, which is flaky at best. Don't do this. If you need to restart a server you should do it manually. The most common cause for getting multiple copies of a server is using the socket manage RESTART button, which is flaky at best. Don't do this. If you need to restart a server you should do it manually.
  
-  - Make sure you are logged into the right machine: ssh ctrscrut +1. Make sure you are logged into the right machine: ssh ctrscrut 
-  - If you are not sure see if the socket manager will tell you. If it doesn't have a look in the file: /ctrscrut/chara/etc/sock_manager/socket_manager.list + 
-  - See if there are any ghosts running \\ +2. If you are not sure see if the socket manager will tell you. If it doesn't have a look in the file: /ctrscrut/chara/etc/sock_manager/socket_manager.list 
-    ps aux | grep esp_server \\ + 
-    Yes, it's hard to know which one it is with the esp servers. You can work out which ones are ghosts by typing the command \\ +3. See if there are any ghosts running 
-    tsockman |grep ctrscrut \\ + 
-    which will give you a list of the servers running on the machine you are interested in. Checking for non-matching PIDs will tell you which processes you need to stop. +ps aux | grep esp_server 
-  - Stop those processes: \\ + 
-    kill -9 PID1 PID2 …. +Yes, it's hard to know which one it is with the esp servers. You can work out which ones are ghosts by typing the command 
-  - Make sure there is no sign of it in the socket manager \\ + 
-    tsockman rm BS +tsockman |grep ctrscrut 
-  - Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2): \\ + 
-    bootlaunch_beamsamp+which will give you a list of the servers running on the machine you are interested in. Checking for non-matching PIDs will tell you which processes you need to stop. 
 + 
 +4. Stop those processes: 
 + 
 +kill -9 PID1 PID2 …. 
 + 
 +5. Make sure there is no sign of it in the socket manager 
 + 
 +tsockman rm BS 
 + 
 +6. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2): 
 + 
 +bootlaunch_beamsamp
  
 ==== "Failed to request position of S1" ==== ==== "Failed to request position of S1" ====
chara/trouble_shooting.txt · Last modified: 2023/11/21 01:42 by charaobs

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki