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 14:41]
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: 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 ==== ==== Telescope clock is not correct ====
Line 178: Line 186:
 ==== E1 Hut and Cooler Communications Recovery ==== ==== 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 S2's acquisition server resides on "S2pi4" computer. Logging on to it (ssh s2pi4) and running bootlaunch will restart it
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__  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. 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 321: Line 330:
 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 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.+3. See if there are any ghosts running
  
-4. Stop those processes: kill -9 PID1 PID2 …. 5. Make sure there is no sign of it in the socket manager tsockman rm BS+ps aux | grep esp_server
  
-5. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2): bootlaunch_beamsamp+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
  
 ==== "Failed to request position of S1" ==== ==== "Failed to request position of S1" ====
Line 350: 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'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 ==== ==== Server display is blank or filled with jibberish ====
Line 384: Line 413:
 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: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. 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 394: 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: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 \\ 
 +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 404: 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> 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. 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 422: 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 ====
chara/trouble_shooting.txt · Last modified: 2024/06/18 00:21 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