Grid Engine Home > Installing > Installing the Software With the GUI Installer >
Tweaking start_gui_installer
The start_gui_installer command will start the Java™ GUI installer. This section describes the command-line options of start_gui_installer, that you might use to affect the performance of the installer in your environment or possibly use as a workaround for yet unknown issues.
The Help text can be invoked by calling the -help option.
master:/sge62u2 # ./start_gui_installer -help
Usage: start_gui_installer [-help] [-resolve_pool=<num>] [-resolve_timeout=<sec>]
[-install_pool=<num>] [-install_timeout=<sec>] [-connect_user=<usr>]
[-connect_mode=windows]
<num> ... decimal number greater than zero
<sec> ... number of seconds, must be greater then zero
<usr> ... user id
If no parameter is specified, the start_gui_installer command is started as if the following command was called:
master:/sge62u2 # ./start_gui_installer -resolve_pool=12 -resolve_timeout=20 -install_pool=8 -install_timeout=120
Every installation generates installation logs in the sge_root/sge_cell/install_logs directory. In addition, a GUI log file is created in a $TEMP directory (usually /var/tmp or /tmp) named SGE_Gui-Installer_Log_<date>.txt.
Description of start_gui_installer Options
| Option | Description |
|---|---|
| -help | displays help for start_gui_installer |
| -resolve_pool=<num> | Defaults to 12. Defines how many hosts can be resolved in parallel when adding new hosts, refreshing their states or when validating hosts. The higher the value the higher load will be generated when resolving hosts, refreshing host states, copying an installation script to remote hosts or validating hosts. |
| -resolve_timeout=<sec> | Defaults to 20 seconds. A timeout value for any operation in a resolve_pool (resolving hosts, refreshing host states, copying an installation script to remote host). Host validation has a timeout which is always equal to 2*resolve_timeout value. Increase the default value if you see hosts with Unreachable state and you are sure that password-less access is working correctly for the connect_user. |
| -install_pool=<num> | Defaults to 8. Defines how many execution daemons can be installed in parallel. The higher the value the higher load will be generated when performing installation tasks. |
| -install_timeout=<sec> | Defaults to 120 seconds. A timeout value for any installation task. Increase the default value if you see that the installation tasks are failing with a Timeout state. |
| -connect_user=<user> | Defaults to current user. User name that will be used when connecting to remote hosts. |
| -connect_mode=windows | When set, each connect_user is prefixed by a host domain (see examples below). This is useful when installing multiple windowd execution hosts that require a different connect_user. |
| -debug | Starts the installer in a debug mode. Prints a lot of output to the terminal. Intended for developer purposes, but may provide additional information when unexpected circumstances occur. |
Using start_gui_installer Options
Installing as a different connect_user
Suppose that you cannot log in as the root user, but can log in as another privileged user with uid=0, called admin. In this case an attempt for a remote connection would be done as current user, but due to uid=0 we would connect as root if root is the primary user with uid=0 on the remote host. Users admin and root would have different home directories and we assume that the password-less access was setup only for the user admin, so the connection without a password as currect user would fail. Invoking the following command will enforce that every remote connection is established as the admin user.
master:/sge62u2 # ./start_gui_installer -connect_user=admin
Installing single Windows execution host
Suppose you want to use the installer to add a single windows execution hosts to the existing cluster. The host is called win-01 and belongs to the WIN-01 domain. Also, the privileged user in this case is Admin (part of Administrators group).
The windows hosts can only be installed remotely from a UNIX/LINUX system and you cannot become an Admin user there. So you might use -connect_user=WIN01+Admin to connect as the correct user directly.
master:/sge62u2 # ./start_gui_installer -connect_user=WIN01+Admin
Installing multiple Windows execution hosts
Suppose you have additional hosts win-02 belonging to the WIN-02 domain and win_vista-01 belonging to the WIN_VISTA-01 domain. All hosts have Administrator user privileges. In this case, you can use the following command to start the GUI installer that will allow you to install all the three Windows execution hosts simultaneously.
master:/sge62u2 # ./start_gui_installer -connect_user=Administrator -connect_mode=windows
Every remote connection to host win-01 would be done as WIN-01+Administrator user.
Every remote connection to host win-02 would be done as WIN-02+Administrator user.
Every remote connection to host win_vista-01 would be done as WIN_VISTA-01+Administrator user.
|
Participate
|
Learn More
|
Sign up or Log in to add a comment or watch this page.