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:23] gail_stargazer |
chara:trouble_shooting [2021/11/09 15:18] gail_stargazer old revision restored (2021/11/09 20:13) |
||
---|---|---|---|
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 Acquisition Server Restart |
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 213: | Line 222: | ||
===== 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 313: | 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. 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' | + | 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' | ||
+ | |||
+ | 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 | ||
+ | |||
+ | 6. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2): | ||
+ | |||
+ | bootlaunch_beamsamp | ||
==== " | ==== " | ||
Line 338: | Line 375: | ||
==== 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 368: | 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. | 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 382: | Line 424: | ||
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 392: | Line 452: | ||
**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 410: | Line 472: | ||
==== 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 ==== |