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 [2018/07/05 11:14]
jones [__Beam Samplers__] 		chara:trouble_shooting [2018/07/05 11:16]
jones [GUIs are frozen]
Line 167: Line 167:
  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.\\ \\  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\\ \\ \\ 
 ==== "Failed to request position of S1" ==== ==== "Failed to request position of S1" ====
-\\  Cosmic Debris reports "Failed to request position of S1" when trying to set the beam order. This indicates that ople is no longer talking to the beam samplers. If the beam sampler server has been restarted recently, then the ople server will also need to be restarted to re-establish the connection.\\ \\  The beam sample server runs on ctrscrut. The ople server tries to open a connection to the beam sampler when it starts. If the beam sampler is not there, or dies,\\  you need to restart the ople server as there is no command to reopen that connection.\\ \\ [[/Trouble%20Shooting#page.troubleshooting|Back to Main Menu]]\\ \\  +\\  Cosmic Debris reports "Failed to request position of S1" when trying to set the beam order. This indicates that ople is no longer talking to the beam samplers. If the beam sampler server has been restarted recently, then the ople server will also need to be restarted to re-establish the connection.\\ \\  The beam sample server runs on ctrscrut. The ople server tries to open a connection to the beam sampler when it starts. If the beam sampler is not there, or dies,\\  you need to restart the ople server as there is no command to reopen that connection.\\ 
-===== __Remote Observing__ =====+=====Remote Observing=====
 \\  \\ 
 ==== VPN connection is not working ==== ==== VPN connection is not working ====
Line 179: Line 179:
   * If either Phase 1 or Phase 2 states say IDLE for a given VPN, then you need to re-establish the connection. To do this, click on the "DROP" button for that VPN. Then click on the "CONNECT" button and wait for the Phase 1 and Phase 2 connections to be established.   * If either Phase 1 or Phase 2 states say IDLE for a given VPN, then you need to re-establish the connection. To do this, click on the "DROP" button for that VPN. Then click on the "CONNECT" button and wait for the Phase 1 and Phase 2 connections to be established.
   * Make sure to close Firefox by using CTRL-Q to quit the program and not just close the window.   * Make sure to close Firefox by using CTRL-Q to quit the program and not just close the window.
-\\ [[/Trouble%20Shooting#page.troubleshooting|Back to Main Menu]]\\ \\  +=====General Problems=====
-===== __General Problems__ =====+
 \\  \\ 
 ==== 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 [[/Trouble%20Shooting#chapter.general.frozenserver|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 ====
  
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