Differences

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

--- chara:trouble_shooting [2021/11/09 14:14]
gail_stargazer
+++ chara:trouble_shooting [2021/11/09 15:18]
gail_stargazer old revision restored (2021/11/09 20:13)
@@ Line 69: / Line 69: @@
 Then restart credone using the desktop icon or by issuing the following command on spooler@mircx: \\ credoneImAcq –no-display
+(the first "–" should be two dashes: - and -).
 ===== Telescopes and Dome Servers =====
@@ Line 109: / Line 111: @@
 ==== Dome Server Restart ====
-To manually start the dome server: 1. Make sure the power to the drives is OFF. 2. Login to the relevant computer as root. For example, type "s1" or "ssh s1" to log on to S1. 3. 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. 4. 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 6. 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.) 7. Turn the power to the drives back on. 8. 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.
+To manually start the dome server:
+  - 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.
+  - 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.)
+  - 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 176: / Line 186: @@
 ==== E1 Hut and Cooler Communications Recovery ====
-{{:chara:files:e1_hut_coms_recovery.pdf|E1 HuT and Cooler Communications Recovery}}  \\  \\ <font 16px/inherit;;inherit;;inherit>**S2 Acquisition Server Restart**</font>
+==== 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 191: / Line 201: @@
 ==== Dome does not open ====
-Is the SPYCAM on and updating? An old image may show the dome is closed, but it has actually started to open. If the dome won't open, try hitting the SLIT CLOSE button on the telescope gui first. It may be that there was a computer or server issue and the computer thinks the dome is open already and won't allow it to open again. Hit the SLIT OPEN button to see if it works now. If it still won't open, go to the bunker and look to see if the power switch is on to the dome. It will be up and red if on. \\
+Is the SPYCAM on and updating? An old image may show the dome is closed, but it has actually started to open. If the dome won't open, try hitting the SLIT CLOSE button on the telescope gui first. It may be that there was a computer or server issue and the computer thinks the dome is open already and won't allow it to open again. Hit the SLIT OPEN button to see if it works now. If it still won't open, go to the bunker and look to see if the power switch is on to the dome. It will be up and red if on.
 Also look to see if the power cable is connected to the computer box. If it's connected up high to the manual dome controls, the cable needs to be brought back to the computer box connector. __Turn the power off first__  to the dome before disconnecting the power cable. Slide it onto the connector at the box and turn the collar to lock it in place. Turn the power back on and see if you can open the dome from the computer in the bunker.
@@ Line 199: / Line 210: @@
 ===== HUT servers =====
+==== I can't change the camera settings on the TV ====
+**CHECK THIS SECTION - THESE ARE VERY CLOSE BUT DIFFERENT PARAGRAPHS:**
 The HUT servers control functions such as beacon and dichroic movements, heater and dehumidifier usage, and various AO functions. An observer may find that the obsgtk is no longer controlling the beacon LED's, beacon flat or dichroic alignments. This happens on occasion with E2 and other scopes. The HUT server may be the cause if it has quit or lost connection or the AOB may be at fault. To see if it is the server, open the HUT gui for the desired telescope from the CHARA menu. If the alignments can be changed from the gui, then the HUT server is ok. You can use the hut gui to continue observing. If the hut gui gives move error messages, cycle the power on the AOB and open a new hut server to restore the connection to the obsgtk. On the POWER gui, turn off the power to the AOB for the offending telescope and turn it back on. Stop the hut server by logging into the appropriate telescope computer and identifying the PID with the bootlaunch_master command and killing the process with the kill -9 #### command. Start the new server via the bootlaunch_master command. Hit REOPEN on the obsgtk to reopen the connection to the HUT server and hit reopen on Cosmic Debris as well.
+The HUT servers control functions such as finder and acq exposure times and gains, heater and dehumidifier usage, and various AO functions. An observer may find that the camera settings do not display or are not adjustable. The HUT server may be the cause if it has quit. To see if it is the server, open the HUT gui for the desired telescope from the CHARA menu. If the camera settings are displayed and the settings can be changed from the gui, then the HUT server is ok. Restart the telescope server to reopen the connection to the HUT server and hit reopen on Cosmic Debris as well. If the gui is not functioning, the HUT server will need to be restarted. The HUT servers run on the computer at each telescope. Find the PID from Sockman for the server you want to shut down. Open a terminal and log into the correct telescope computer (for example, type "s1" to log on to S1). Use the command "ps aux | grep HUT" to find the process you need to shut down. The number should match the PID from Sockman. Kill the process by typing "kill -9 pid" where pid is the process number and remove the entry from Sockman with the REMOVE button on the gui or by command line. Restart the hut server using the new "bootlaunch_hut" command described in the section on Restarting Servers.
+If the server won't restart, a reboot of the power supply in the telescope bunker might be necessary. The power supply that controls the acquisition and finder cameras as well as their controllers is located on top of the computer rack in each bunker. The power supply has green readouts of volts and current. After turning the power off for 10 seconds and back on, try restarting the server from the computer in the bunker to see if it starts cleanly. If so, then restart the telescope server, reopen the connection to the telescope gui, and hit REOPEN on Cosmic Debris. Part of the HUT server also controls the AO table. If the AOB part of the HUT server doesn't work, then the power supply on the back of the AO table in the telescope dome might need recycling. This power supply controls the actuators at M2 and the AO table. The power supply box is a 6×9 inch aluminum box on the back of the AO table, behind the keyboard and monitor. Turn it off with the power button on the bottom edge of the box, wait 5 seconds and turn it back on. The HUT server should now restart cleanly. Restart the telescope server as well to make the connections to the telescope gui. Hit REOPEN in Cosmic Debris if you are observing to make all needed connections.
 ===== Tiptilt Server. (These sections apply to the old lab tiptilt system retired in April 2021) =====
+[[:chara:old_lab_tiptilt_server|Instructions for the old lab tiptilit system are archived here.]]
 The tiptilt server controls the CCD based tiptilt detection system. \\  \\
@@ Line 303: / Line 324: @@
 ==== Restarting the Beam Sampler Server ====
-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. 1. Make sure you are logged into the right machine: ssh ctrscrut 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 3. See if there are any ghosts running 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 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. 4. Stop those processes: kill -9 PID1 PID2 …. 5. Make sure there is no sign of it in the socket manager tsockman rm BS 5. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2): bootlaunch_beamsamp
+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
+. 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
+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
+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.
+. 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" ====
@@ Line 328: / Line 375: @@
 ==== GUIs are frozen ====
-Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn't come up, Sockman may be hung up. Follow the Sockman restart procedure in the text file on the desktop if it won't respond. Hit [REOPEN] on the gui to see if it reconnects with its server. if that does not fix it, the server may be dead. From the LIST on Sockman, select the server suspected of being frozen. Ping it and if it reports back as being dead, see [[:chara:trouble_shooting#server_is_frozen|Server is frozen]] section below. Telescope guis often freeze. Hit reopen on the gui to bring it back to life. Hitting [MOVE] on the telescope gui before the star has stopped moving can cause the gui to freeze. Avoid doing this. Close the dead one and open a new one to fix the problem.
+Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn't come up, Sockman may be hung up. Follow the Sockman restart procedure in the text file on the desktop if it won't respond.
+Hit [REOPEN] on the gui to see if it reconnects with its server. if that does not fix it, the server may be dead. From the LIST on Sockman, select the server suspected of being frozen. Ping it and if it reports back as being dead, see [[:chara:trouble_shooting#server_is_frozen|Server is frozen]] section below.
+Telescope guis often freeze. Hit reopen on the gui to bring it back to life. Hitting [MOVE] on the telescope gui before the star has stopped moving can cause the gui to freeze. Avoid doing this. Close the dead one and open a new one to fix the problem.
 ==== Server display is blank or filled with jibberish ====
@@ Line 358: / Line 409: @@
 If an object is not in SIMBAD (such as a recently discovered nova), then you must enter the object manually using the instructions below.
-==== Finding a star in the CHARA database ====
+**Finding a star in the CHARA database**
 Here is an example of how to find the CHARA number of a star, nova, or AGN that is already in the CHARA database:
-[ctrscrut:502] dbadd NGC 4151 Object "NGC 4151" found as CHARA number: 320263
+[ctrscrut:502] dbadd NGC 4151 \\
+Object "NGC 4151" found as CHARA number: 320263
 Note: If the target information stored in the CHARA database does not match SIMBAD, then dbadd will provide the coordinates and magnitudes listed in SIMBAD, and it will also list the CHARA numbers of objects in the database located within 10 arcsec. Please check these nearby entries before adding a new star to the database.
@@ Line 372: / Line 424: @@
 Here is an example of how to add an object to the CHARA database:
-[ctrscrut:534] dbadd BD 41 3807 SIMBAD found this for "BD 41 3807":
+[ctrscrut:534] dbadd BD 41 3807
-ID 2MASS_J20340850 4136592 CHARA 320414 2000.0 CAT8 2MASS_J20340850 4136592 RA 20 34 08.5148 DEC 41 36 59.408 PMRA -2.32 PMDEC -3.87 PAR 0.58 RVEL -27.50 VMAG 10.03 HMAG 6.23 KMAG 5.99 SP O5.5Ifc END
+SIMBAD found this for "BD 41 3807":
-Is the above the object you are looking for? [y/n] y Added "BD 41 3807" to the database.
+ID 2MASS_J20340850 4136592 \\
+CHARA 320414 \\
+.0 \\
+CAT8 2MASS_J20340850 4136592 \\
+RA 20 34 08.5148 \\
+DEC 41 36 59.408 \\
+PMRA -2.32 \\
+PMDEC -3.87 \\
+PAR 0.58 \\
+RVEL -27.50
+VMAG 10.03 \\
+HMAG 6.23 \\
+KMAG 5.99 \\
+SP O5.5Ifc \\
+END
+Is the above the object you are looking for? [y/n] y \\
+Added "BD 41 3807" to the database.
 In the example above, the object "BD 41 3807" has been added to the database as CHARA number 320414.
@@ Line 382: / Line 452: @@
 **Targets that are not in SIMBAD**
-Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> for a star not in the SIMBAD database returns the message "Simbad is unable to find an object matching <star designation>. Try using a different catalog designation, or use the "-m" switch to add the object manually." The command dbadd -m is used by entering the star name and coordinates in this format:
+Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> for a star not in the SIMBAD database returns the message "Simbad is unable to find an object matching <star designation>. Try using a different catalog designation, or use the "-m" switch to add the object manually."
-Usage: dbadd -m <name> <RA> <Dec> <name>
+The command dbadd -m is used by entering the star name and coordinates in this format:
-Object ID (no spaces) <RA> : XXhXXmXX.X or XXhXX.X (no spaces) <Dec> : XXdXXmXX.X or XXdXX.X (no spaces)
+Usage: dbadd -m <name> <RA> <Dec> \\  \\
+<name>: Object ID (no spaces) \\  \\
+<RA> : XXhXXmXX.X or XXhXX.X (no spaces) \\  \\
+<Dec> : XXdXXmXX.X or XXdXX.X (no spaces) \\  \\
 There are cases where an object is not in SIMBAD and doesn't return a result in dbadd, but is in fact in the CHARA database. Novae and AGN's are the likely objects that cause this result. At times, objects have multiple entries and several CHARA numbers since the names can be so unique. A system will be developed to find these entries without knowing or having a conventional database designation.
@@ Line 400: / Line 472: @@
 ==== Adding an anchor to the wiki page ====
-To add an anchor to the wikipage, type the following where you want the anchor inserted (without the spaces between the symbols): [ [ #AnchorName ] ] Highlight the text you want to be a link to the anchor, click the link symbol above and select anchor. Select a page(such as Trouble Shooting) where the anchor is located and give the same name for the anchor.
+To add an anchor to the wikipage, type the following where you want the anchor inserted (without the spaces between the symbols): \\
+[ [ #AnchorName ] ]
+Highlight the text you want to be a link to the anchor, click the link symbol above and select anchor. Select a page(such as Trouble Shooting) where the anchor is located and give the same name for the anchor.
 ==== Displays for the MIRC-X wolverine2 monitors ====

The CHARA Array Wiki

User Tools

Site Tools

Differences

Page Tools