Grid Engine Home > Installing > Installing the Software With the GUI Installer >
Understanding Host and Installation States
This section lists the different installation states that you might encounter while using the GUI installer. The installation states can be divided into the following three categories.
Host Resolving
When a new host is added in the Select hosts screen, the host name State field is immediately set to New unknown host and host name resolving process is initiated. The host name is marked as Reachable only if the architecture of the host can be retrieved. All the other states specify an error. The GUI installer cannot perform any installation on such a host. The following table lists all possible states.
| State | Description |
|---|---|
| New unknown host | Initial state. When the host name is added, the GUI installer immediately starts resolving the host name or IP address of the host, if there are available threads in the resolve pool. |
| Resolving | Temporary state. The host is being resolved based on the host name or IP address by using the default name service. |
| Unknown host | Final state. The host cannot be resolved by the name service. |
| Resolvable | Temporary state. After the host is resolved, the GUI installer immediately tries to retrieve the host's architecture, if there are available threads in the resolve pool. |
| Contacting | Temporary state. The host has been resolved and the host's architecture is being retrieved. |
| Missing remote file | Final state. Missing file '$SGE_ROOT/util/arch' on remote host. Is the sge-root path the same for the remote host and the local host? If not, fix the path or refer Using Path Aliasing. |
| Reachable | Final state. The host architecture cannot be retrieved. Password-less ssh or rsh access to remote hosts is working properly. |
| Unreachable | Final state. The host architecture cannot be retrieved. Password-less ssh or rsh access to remote hosts is not working properly. See How to Configure Password-less Access for more information. |
| Canceled | Final state. The user has canceled the host resolving process. |
Host Validating
After the hosts have been resolved and their architecture has been retrieved, they are moved to the Reachable tab in the Select hosts screen. You can install Sun Grid Engine on a host that is in the Reachable state. While clicking the Install button, the GUI installer first invokes additional remote host validation. If the installer discovers any configuration errors (see RED and ORANGE states in the list below), the installation is not initiated and the appropriate error message is displayed. You can return to the Select hosts screen and proceed with the installation if you wish.
| State | Description | Problem Resolution |
|---|---|---|
| Copy timeout | Timeout occurred when copying check_host or install_component files. See tooltip for the exact file name. |
Try again (press Install button one more time). If timeout reoccurs, save your host list to a file, stop the installer and restart it with increased timeout values. See tweaking start_gui_installer. |
| Copy failed | Copying files check_host or install_component to the remote host failed. See tooltip for the exact file name. |
Try again (press Install button one more time). If problems reoccurs try to copy a any file with scp or rcp to verify these commands work properly. If not make sure they do before new installation attempt. |
| Permission denied | Either of Berkeley DB, qmaster, execution daemon spool directory or JMX keystore file is not writable. See tooltip for the exact message. Installation will most likely fail, if you proceed anyway. |
Did you start the installation as root? What permissions are for the first existing directory? Are you on a NFS file system with root mapped to nobody? Is the UID for the admin user the same on the local and remote machine? |
| Admin user missing | The admin user entered in the main configuration screen does not exist on the remote machine. | Setup the host properly so that name service provides the name properly to the remote machine (or create the user locally). |
| Directory exists | Berkeley DB spool directory already exists! | Check the remote host for existing Berkeley DB installations. Remove the existing directory. |
| Wrong FS type | Specified Berkeley DB spool directory is on a local file system. | Go back to the spooling configuration screen and choose a proper local directory. |
| Unknown error | Unknown error has occurred. | Try again (press Install button one more time). If reoccurring, ignore and try to install anyway. |
| Reachable | Validation did not discover any issues for this remote host. | |
| Canceled | User canceled further host validation. |
Installation States
When the installation is started the host list with the chosen components is transformed to a task list. The task list is better suited to handle dependencies. These are the states one may encounter during the installation.
| State | Description |
|---|---|
| Waiting | Task is waiting to be executed. |
| Processing | Temporary state. Task is being processed. |
| Timeout | Task did not finish before timeout value has been reached. |
| Success | Task finished successfully. |
| Failed | Task finished unsuccessfully. Click the Log button to get more information. |
| Failed due to dependency | Task was not started, because it depended on a task that failed. Click the Log button to get more information. |
| Component already exists | Task was not started. The installation detected a previous conflicting component installation. Click the Log button to get more information. Remove any remains of the old installation, before trying again. |
| Canceled | User canceled the installation process. |
|
Participate
|
Learn More
|
Sign up or Log in to add a comment or watch this page.