Differences

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

--- chara:trouble_shooting [2021/11/09 15:10]
gail_stargazer
+++ chara:trouble_shooting [2021/11/09 15:30]
gail_stargazer
@@ Line 113: / Line 113: @@
 To manually start the dome server:
-  - Make sure the power to the drives is OFF.
+. Make sure the power to the drives is OFF.
-  - Login to the relevant computer as root. For example, type "s1" or "ssh s1" to log on to S1.
-  - Work out the process ID number (PID), either with the command (s1:1001) tsockman get dome_S1 Name : dome_S1 Machine : s1.chara-array.org PID : 29953 Commands : -1 Data : -1 Message : 4002 Restart : /usr/local/bin/dome_server -A33.7441 S1 or with (s1:1003) ps aux | grep dome theo 4473 0.0 0.0 61188 748 pts/3 S 10:45 0:00 grep dome observe 29953 18.5 0.4 35596 9860 ? Sl Apr21 416:11 /usr/local/bin/dome_server -A33.7441 S It can also be found by pulling up the LIST on SOCKMAN and selecting the relevant dome. So in this case the PID is 29953.
+. Login to the relevant computer as root. For example, type "s1" or "ssh s1" to log on to S1.
-  - Try and stop the server gracefully: kill -2 29953 5. You should then check that the server has indeed stopped: [s1:600] tsockman get dome_S1 Name : dome_S1 Machine : s1.chara-array.org PID : 15635 Commands : -1 Data : -1 Message : 2008 Restart : /usr/local/bin/dome_server -A41.0166 S1 If the socket manager still thinks it's running you will need to stop it forcefully: kill -9 29953; tsockman rm dome_S1
-  - Restart the dome server by copying the command at the end of the /etc/rc.local file: [s1:602] more /etc/rc.local <<< Press space bar or enter to scroll through file>>> #Run the dome server /usr/local/bin/tsockman remove dome_S1 /usr/local/bin/dome_server -A41.0166 S1 & (Note: the part of the command that saves information to /var/log/dome_S1.log has been removed.)
+. Work out the process ID number (PID), either with the command
-  - Turn the power to the drives back on.
-  - Hit REOPEN and ENABLE on the domegtk, and type "otcs" in the telescope server. You may have to reinitialize the scope on a bright star. If the powers were turned off quickly when the problem was noticed, the position of the scope should be retained and slewing to a bright star will get it in the finder. If not, you may need to go out to the telescope to find the bright star to reacquire the scopes position.
+(s1:1001) tsockman get dome_S1 \\
+Name : dome_S1 \\
+Machine : s1.chara-array.org \\
+PID : 29953 \\
+Commands : -1 \\
+Data : -1 \\
+Message : 4002 \\
+Restart : /usr/local/bin/dome_server -A33.7441 S1 \\  \\
+or with \\
+(s1:1003) ps aux | grep dome \\
+theo 4473 0.0 0.0 61188 748 pts/3 S+ 10:45 0:00 grep dome \\
+observe 29953 18.5 0.4 35596 9860 ? Sl Apr21 416:11 /usr/local/bin/dome_server -A33.7441 S \\  \\
+It can also be found by pulling up the LIST on SOCKMAN and selecting the relevant dome. \\  \\
+So in this case the PID is 29953. \\  \\
+. Try and stop the server gracefully: kill -2 29953
+. You should then check that the server has indeed stopped: \\  \\
+[s1:600] tsockman get dome_S1 \\
+Name : dome_S1 \\
+Machine : s1.chara-array.org \\
+PID : 15635 \\
+Commands : -1 \\
+Data : -1 \\
+Message : 2008 \\
+Restart : /usr/local/bin/dome_server -A41.0166 S1 \\  \\
+If the socket manager still thinks it's running you will need to stop it forcefully: kill -9 29953; tsockman rm dome_S1
+. Restart the dome server by copying the command at the end of the /etc/rc.local file:
+[s1:602] more /etc/rc.local \\
+<<< Press space bar or enter to scroll through file>>> \\  \\
+#Run the dome server \\  \\
+/usr/local/bin/tsockman remove dome_S1 \\
+/usr/local/bin/dome_server -A41.0166 S1 & \\  \\
+(Note: the part of the command that saves information to /var/log/dome_S1.log has been removed.)
+. Turn the power to the drives back on.
+. Hit REOPEN and ENABLE on the domegtk, and type "otcs" in the telescope server.
+You may have to reinitialize the scope on a bright star. If the powers were turned off quickly when the problem was noticed, the position of the scope should be retained and slewing to a bright star will get it in the finder. If not, you may need to go out to the telescope to find the bright star to reacquire the scopes position.
 ==== Telescope clock is not correct ====
@@ Line 145: / Line 185: @@
 ==== Telescope is tracking poorly, overshooting in slew, oscillating. ====
-This might mean that the gain for the tracking servo is wrong. Note that changing this gain can be dangerous, especially if you set it too high as that can cause the telescope to oscillated and damage the drives. Please only do this if you are very very sure that it is necessary. Symptoms of bad gain are: The scope over shoots the position while slewing. The star will be seen to move out of the window and may come back after a few seconds. This means the slewing gain is too low. The scope oscillates when tracking or after a slew. The star will be tracing an ellipse, figure eight or other looping shape. This means the tracking gain is too low. You can damp this out with the telescope or dome gui by disabling the scope, then re-enabling it. Adjust the gain upward and watch it on the next slew. In all cases if either gain is too high the scope will go into "Fog Horn" mode, which is bad. You always want to use the lowest gain that still allows the scope to work as best as possible. If the tiptilt tells you the scope is oscillating slowly, the gain may be too low. If it is oscillating quickly it may be too high. On 10-22-2016, the gain settings were: | Scope | AZ Slewing || EL Slewing || AZ Tracking || EL Tracking || Date Updated |
+This might mean that the gain for the tracking servo is wrong. Note that changing this gain can be dangerous, especially if you set it too high as that can cause the telescope to oscillated and damage the drives. Please only do this if you are very very sure that it is necessary. Symptoms of bad gain are: The scope over shoots the position while slewing. The star will be seen to move out of the window and may come back after a few seconds. This means the slewing gain is too low. The scope oscillates when tracking or after a slew. The star will be tracing an ellipse, figure eight or other looping shape. This means the tracking gain is too low. You can damp this out with the telescope or dome gui by disabling the scope, then re-enabling it. Adjust the gain upward and watch it on the next slew. In all cases if either gain is too high the scope will go into "Fog Horn" mode, which is bad. You always want to use the lowest gain that still allows the scope to work as best as possible. If the tiptilt tells you the scope is oscillating slowly, the gain may be too low. If it is oscillating quickly it may be too high. On 10-22-2016, the gain settings were:
+|Scope|AZ Slewing| |AZ Slewing| |AZ Tracking| |EL Tracking| |Date Updated|
 | |Gain|Fn|Gain|Fn|Gain|Fn|Gain|Fn| |
 |S1|7|4|4|3|16|4|10|7|10-26-2017|
@@ Line 186: / Line 227: @@
 ==== E1 Hut and Cooler Communications Recovery ====
-====   E1 HuT and Cooler Communications Recovery   \\  \\  S2 Acquisition Server Restart  ====
+{{:chara:files:e1_hut_coms_recovery.pdf|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
@@ Line 326: / Line 369: @@
 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
+. 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 \\
+. 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 \\
+. 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.
+. Stop those processes:
+kill -9 PID1 PID2 ….
+. Make sure there is no sign of it in the socket manager
+tsockman rm BS
+. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2):
+bootlaunch_beamsamp
 ==== "Failed to request position of S1" ====

The CHARA Array Wiki

User Tools

Site Tools

Differences

Page Tools