Installing a Linux Indexer worker node

You can choose to install the Indexer on a server installed with Red Hat Enterprise Linux 6.0 and above. The Linux indexer works exactly the same way as the Windows indexer.

Before you install the Indexer on the Linux server, ensure the following:

Installing the worker node

  1. SSH to the Linux server where you want to install the worker node . You can install the package either as root or as non-root user. Ensure that you are logged in as that user.
  2. Run the following command to launch the installer package:

    sh Veritas_DataInsight_linux_5_2_0_N_<RHELVER>_x64.sh, where N is the build number, and RHELVER is RHEL6 or RHEL7 depending on the version of your operating system.

  3. The Welcome to the Veritas Data Insight Setup Wizard window appears. Click Next.
  4. In the License Agreement window, select I accept the agreement, and click Next.
  5. In the Select Destination Directory window, browse to the directory in which you want the Indexer to be installed. By default, the destination directory is /opt/DataInsight.

    When installing as non-root, ensure that the user has write privileges to the install location.

  6. Click Next.
  7. In the Configure Data Directory window, browse to the location where you want to store the product data.

    Select a location with enough free space and high-performance disks.

  8. In the Worker Node address window, enter the Fully Qualified Host Name (FQHN) or IP address of the host. Ensure that the Management Server and the other worker nodes are able to resolve this hostname.
  9. In the Configure Networking window, enter the following information:

    Communication Service Port

    See About Communication Service.

    Configuration Service Port

    Configuration service is a process that provides interface to configuration and other product data stored on the local system. This service port does not need to be accessible outside the host machine.

    Note:

    The installer validates whether the appropriate ports are free to accept connections.

  10. To register the worker node with the Management Server after you exit setup, select the Launch Worker Node Registration Wizard after exit checkbox.

    See Registering the worker node and the Portal node.

  11. To exit setup, click Finish.
  12. Optionally, to use an alternate location for the log files, edit the following files that are located in the /opt/DataInsight/conf directory, to replace /opt/DataInsight/log with the new log location:

    cli_logging.properties

    dscli_logging.properties

    commd_logging.properties

    watchdog_logging.properties

    webserver_logging.properties

    Export the new log directory using the following command:

    export MATRIX_LOG_DIR=/DataInsight/log

    Add the export entry to .bash_profile file of the user to reflect the change when you restart the system.

    Execute the following command to update the profile path:

    source .bash_profile

    Note:

    If you are installing Data Insight as non-root, but have, at an earlier time, installed and run the services as root, you must first delete the following files:

    rm /tmp/i4jdaemon__DIdata_DataInsight_bin_DataInsightComm

    rm /tmp/i4jdaemon__DIdata_DataInsight_bin_DataInsightWatchdog

    rm /var/run/queryd.pid

  13. When installing as a non-root user, after you have registered this node with the Management Server, add following entries to /etc/rc.local to automatically start the services after you restart the system:
    su  -  <name of non-root user>
    # export MATRIX_LOG_DIR=/DataInsight/log (Optional)
    /opt/DataInsight/bin/DataInsightConfig start
    /opt/DataInsight/bin/DataInsightComm start
    
    /opt/DataInsight/bin/DataInsightWatchdog start
    
    logout

    To stop services during shutdown, add the following entries to /etc/rc.local.shutdown:

    /opt/DataInsight/bin/DataInsightWatchdog stop
    /opt/DataInsight/bin/DataInsightComm stop
    /opt/DataInsight/bin/DataInsightConfig stop

Note:

The DataInsightConfig service does not start after registration if the queryd.lock is present in the /tmp folder. The lock file is present if the installation is done using root, or when the machine is restarted. You must delete the queryd.lock file before you restart the DataInsightConfig service.