Trafodion Scanner

This page describes the Trafodion Scanner.

Introduction

The Trafodion Scanner checks the cluster for attributes that commonly cause installation issues, runtime performance problems, and so on. In addition, various system information is collected for future reference, such as to aid with troubleshooting.

The Trafodion Scanner is automatically invoked by the trafodion_install script, at the beginning of the Trafodion installation. The trafodion_install script will abort if any configuration errors are discovered by the Scanner. You will need to correct such errors before re-running the trafodion_install script.

NOTE: If necessary, it is possible to suppress automatic Scanner invocation by specifying the --no_scanner parameter with the trafodion_install script: ./trafodion_install --no_scanner. For example, this may be necessary in order to install Trafodion on a non-standard cluster configuration, where Scanner errors would otherwise prevent the installation from proceeding.

The Trafodion Scanner may take several minutes to complete, depending on the size and speed of your cluster. It executes in two stages:

1. Checks basic cluster prerequisites. This stage validates the following set of basic prerequisites. If an issue is detected, an error will be reported. You will need to correct any such errors before continuing with the Trafodion installation.
   • All of the specified nodes can be accessed via passwordless ssh.
   • The user running this script has full sudo access, and it is correctly configured on all of the specified nodes.
2. Collects system information and checks cluster configuration. This stage executes the configuration-recording commands as well as the configuration and consistency checks specified in the Configuration File. When it completes, you will see a message similar to this one:

   ******* SUMMARY *******
   Completed Execution on 4 nodes: node1 node2 node3 node4
   Results:
     node2 - All checks PASSED
     node1, node3 - YumAndInternetConnection check FAILED [warning]
     node4 - HardwarePlatform check FAILED [error], MinNumCores check FAILED [warning]
   
   Additional details in log file: /var/log/trafodion/trafodion_scanner_2015-05-01-18-40-21.log
   

   • If any checks FAILED with [error], it is required that you correct the relevant cluster attributes before continuing with the Trafodion installation. For example, the sample output above shows that the HardwarePlatform check failed with [error] on node4.
   • If any checks FAILED with [warning], it is recommended that you correct the relevant cluster attributes before continuing with the Trafodion installation. For example, the sample output above shows that the YumAndInternetConnection check failed with [warning] on node1 and node3 and that the MinNumCores check failed with [warning] on node4.

   You can find the specific details about each check failure in the Scanner log file trafodion_scanner_<timestamp>.log (the name and fully qualified path of the log file is displayed at the end of Scanner execution, as shown in the example above). You can search the log file using the name of the check that failed, for example, "HardwarePlatform". Also, you may find it helpful to read the check descriptions and notes for Cluster Configuration Checking andCluster Consistency Checking.

Manual Invocation

The Trafodion Scanner can be invoked manually, at any time. For example, you can run it after making adjustments to your cluster, to verify that no configuration issues are present. Here are the steps:

IMPORTANT: These steps should be done on the same node where you ran the trafodion_install script. Login with the same User ID that was used to run the trafodion_install script (enabled with sudo and passwordless ssh access to all nodes of the cluster).

1. Change to the installer tools directory:

   cd $HOME/trafodion_downloads/installer/tools
   

2. Run the trafodion_scanner script. You don't need to specify any parameters. The trafodion_scanner script automatically uses the cluster information collected by the trafodion_install script. If the needed information is not available, you will be prompted to enter it.

   ./trafodion_scanner
   

Configuration File

The default Trafodion Scanner configuration file is $HOME/trafodion_downloads/installer/tools/trafodion_scanner.cfg. There are comments at the top of the file explaining the configuration specification format. There are three sections with specifications for Cluster Configuration Recording, Cluster Configuration Checking, and Cluster Consistency Checking.

Cluster Configuration Recording

The Trafodion Scanner collects various system information for future reference, such as to aid with troubleshooting. This is done by executing one or more commands on each node in the cluster and recording the output in the log file. The following information is collected per the default configuration file:

Cluster Configuration Checking

The Trafodion Scanner checks the cluster for attributes that will commonly cause Trafodion installation issues, runtime performance problems, and so on. These attributes are divided into two categories: required and recommended. The checks for required attributes have a severity level of [error], while the checks for recommended attributes have a severity level of [warning]. Checks are done by executing one or more commands on each node in the cluster and comparing the output against an expected result. The following checks are carried out per the default configuration file:

Cluster Consistency Checking

The Trafodion Scanner checks the consistency among cluster nodes for attributes that will commonly cause Trafodion installation issues, runtime performance problems, and so on. These attributes are divided into two categories: required and recommended. The checks for required attributes have a severity level of [error], while the checks for recommended attributes have a severity level of [warning]. Checks are done by executing one or more commands on each node in the cluster and comparing the output among these nodes. The following checks are carried out per the default configuration file: