This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
chara:trouble_shooting [2021/11/09 14:16] gail_stargazer |
chara:trouble_shooting [2021/11/09 15:10] gail_stargazer |
||
---|---|---|---|
Line 111: | Line 111: | ||
==== Dome Server Restart ==== | ==== Dome Server Restart ==== | ||
- | To manually start the dome server: | + | 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 " | ||
+ | - 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 : / | ||
+ | - 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 : / | ||
+ | - Restart the dome server by copying the command at the end of the / | ||
+ | - Turn the power to the drives back on. | ||
+ | - Hit REOPEN and ENABLE on the domegtk, and type " | ||
==== Telescope clock is not correct ==== | ==== Telescope clock is not correct ==== | ||
Line 178: | Line 186: | ||
==== E1 Hut and Cooler Communications Recovery ==== | ==== E1 Hut and Cooler Communications Recovery ==== | ||
- | {{: | + | ==== E1 HuT and Cooler Communications Recovery |
S2's acquisition server resides on " | S2's acquisition server resides on " | ||
Line 193: | Line 201: | ||
==== Dome does not open ==== | ==== 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__ | 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__ | ||
Line 201: | Line 210: | ||
===== HUT servers ===== | ===== 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 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, | ||
+ | |||
+ | 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' | ||
===== Tiptilt Server. (These sections apply to the old lab tiptilt system retired in April 2021) ===== | ===== Tiptilt Server. (These sections apply to the old lab tiptilt system retired in April 2021) ===== | ||
+ | |||
+ | [[: | ||
The tiptilt server controls the CCD based tiptilt detection system. \\ \\ | The tiptilt server controls the CCD based tiptilt detection system. \\ \\ | ||
Line 305: | Line 324: | ||
==== Restarting the Beam Sampler Server ==== | ==== 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. | + | 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' | ||
+ | - See if there are any ghosts running | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | - Stop those processes: | ||
+ | | ||
+ | - Make sure there is no sign of it in the socket manager | ||
+ | | ||
+ | - Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2): \\ | ||
+ | | ||
==== " | ==== " | ||
Line 330: | Line 363: | ||
==== GUIs are frozen ==== | ==== GUIs are frozen ==== | ||
- | Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn' | + | Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn' |
+ | |||
+ | 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 [[: | ||
+ | |||
+ | 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 ==== | ==== Server display is blank or filled with jibberish ==== | ||
Line 360: | Line 397: | ||
If an object is not in SIMBAD (such as a recently discovered nova), then you must enter the object manually using the instructions below. | 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: | 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: | + | [ctrscrut: |
+ | 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. | 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 374: | Line 412: | ||
Here is an example of how to add an object to the CHARA database: | Here is an example of how to add an object to the CHARA database: | ||
- | [ctrscrut: | + | [ctrscrut: |
- | 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 " |
- | 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 \\ | ||
+ | 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 | ||
+ | |||
+ | 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. | In the example above, the object "BD 41 3807" has been added to the database as CHARA number 320414. | ||
Line 384: | Line 440: | ||
**Targets that are not in SIMBAD** | **Targets that are not in SIMBAD** | ||
- | Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> | + | Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> |
- | Usage: | + | The command |
- | + | ||
- | Object ID (no spaces) <RA> : XXhXXmXX.X or XXhXX.X (no spaces) < | + | |
+ | Usage: dbadd -m < | ||
+ | < | ||
+ | <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' | There are cases where an object is not in SIMBAD and doesn' | ||
Line 402: | Line 460: | ||
==== Adding an anchor to the wiki page ==== | ==== 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 ==== | ==== Displays for the MIRC-X wolverine2 monitors ==== |