User Tools

Site Tools


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
chara:trouble_shooting [2019/05/24 19:31]
gail_stargazer
chara:trouble_shooting [2019/05/24 19:41] (current)
gail_stargazer
Line 28: Line 28:
 ==== Restarting Servers using the bootlaunch paradigm ==== ==== Restarting Servers using the bootlaunch paradigm ====
  
-If a server is not running or Socket Manager reports that a server is dead, then look at the socket manager list to find out what computer the server runs on ([[:​chara:​socket_manager_list_file|socket_manager.list]]). You can also look at the up-to-date file by opening a terminal window and typing "less /​ctrscrut/​chara/​etc/​socket_manager/​socket_manager.list"​. \\ +If a server is not running or Socket Manager reports that a server is dead, then look at the socket manager list to find out what computer the server runs on ([[:​chara:​socket_manager_list_file|socket_manager.list]]). You can also look at the up-to-date file by opening a terminal window and typing "less /​ctrscrut/​chara/​etc/​socket_manager/​socket_manager.list"​
- \\ + 
-A number of servers use an interim bootlaunch paradigm to restart. This is confined to servers that run on ubuntu machines, namely the telescope bunker computers and gps. The basic syntax is "​bootlaunch_<​server>"​ where "<​server>"​ is replaced by the server the script is designed to address. The scripts have a number of safeties built in, so it is safe to run them even if a server is already running – they just output the process ID of the running server. The scripts also take care of the entry in socket manager as well any serial port lock files. All the pertinent information is world writeable, so one should be able to run a bootlaunch script as observe. \\ +To restart a server, log on to the machine that runs the server and type "​bootlaunch_master"​. ​ This script will go through the list of executables and will check which servers are running. ​ If a server isn't running it bootlaucn_master will remove it from socket manager, clear the lock file, and relaunch the server. ​ The instructions below describe how to restart individual servers, but this should not be necessary anymore. \\  \\ A number of servers use an interim bootlaunch paradigm to restart. This is confined to servers that run on ubuntu machines, namely the telescope bunker computers and gps. The basic syntax is "​bootlaunch_<​server>"​ where "<​server>"​ is replaced by the server the script is designed to address. The scripts have a number of safeties built in, so it is safe to run them even if a server is already running – they just output the process ID of the running server. The scripts also take care of the entry in socket manager as well any serial port lock files. All the pertinent information is world writeable, so one should be able to run a bootlaunch script as observe. \\  \\ One thing of note about the output of the bootlaunch scripts, they call a number of other programs which themselves have output that may be misleading in the context of bootlaunch. Chief among these is the output of "​tsockman"​. If a server stopped unexpectedly,​ it may leave behind an entry in the socket manager. In order to launch a new server, one needs to clean out the socket manager entry if it is there. To do that, "​tsockman remove <​entry>"​ is called to remove "<​entry>"​ before the new server is launched. If there is no entry, tsockman will respond with "​Process by that name does not exist"​. THIS IS NORMAL and is not indicative of an error. The server in question launched (without fanfare) right after that output text. \\  \\ Here are the available bootlaunch scripts as of June 2017: \\  \\ gps computer:
- \\ +
-One thing of note about the output of the bootlaunch scripts, they call a number of other programs which themselves have output that may be misleading in the context of bootlaunch. Chief among these is the output of "​tsockman"​. If a server stopped unexpectedly,​ it may leave behind an entry in the socket manager. In order to launch a new server, one needs to clean out the socket manager entry if it is there. To do that, "​tsockman remove <​entry>"​ is called to remove "<​entry>"​ before the new server is launched. If there is no entry, tsockman will respond with "​Process by that name does not exist"​. THIS IS NORMAL and is not indicative of an error. The server in question launched (without fanfare) right after that output text. \\ +
- \\ +
-Here are the available bootlaunch scripts as of June 2017: \\ +
- \\ +
-gps computer:+
  
   * bootlaunch_beamsamp – Starts the beam sampler servers, BS1 and BS2.   * bootlaunch_beamsamp – Starts the beam sampler servers, BS1 and BS2.
chara/trouble_shooting.txt · Last modified: 2019/05/24 19:41 by gail_stargazer