Running dr_install.sh returns errors

Article Id: 38019
Status: Published
Updated On: 07-05-2019 13:40
Legacy Id: TEC1382495
Products:
CA Infrastructure Management , CA Infrastructure Management , CA Performance Management - Usage and Administration , CA Performance Management - Data Polling
Issue/Introduction:

During the installation of a Performance Management Data Repository Vertica Database with multiple nodes the install fails.

Running the dr_install.sh script after successful run of dr_validate.sh returns the following errors in the output of the install run, and in the install_log_install_<Date>_<Time>.log file.
 

>> Validating node and cluster prerequisites...

Error: Command failed on '<Node_IP>':
    VERT_DBA_USR=pmdbadmin VERT_DBA_DATA_DIR=/drdata/data VERT_DBA_HOME=/home/pmdbadmin VERT_DBA_GRP=verticadba /opt/vertica/oss/python/bin/python -m vertica.local_coerce
    returncode = -1
Error: Command failed on 'Node_IP':
    VERT_DBA_USR=pmdbadmin VERT_DBA_DATA_DIR=/drdata/data VERT_DBA_HOME=/home/pmdbadmin VERT_DBA_GRP=verticadba /opt/vertica/oss/python/bin/python -m vertica.local_coerce
    returncode = -1
System prerequisites failed.  Threshold = WARN
    Hint: Fix above failures or use --failure-threshold

Installation FAILED with errors.

Cause:

Two known causes have been observed generating this error.

  1. The most common cause is related to large log in banners set up in the system that show up when first logging in and connecting in a terminal window. When the install runs on the remote nodes, these banners throw off the installation processing.
  2. A less common cause is related to shared /etc/mtab files. When this takes place and there are an excessive number of entries, the installation times out going through it's system checks against the many entries.

Environment:

All supported Performance Management Releases

Resolution:

To resolve this problem depending on the cause complete the following.

Large Banners

  1. Review the following files to find any with entries that match the banners seen when logging into the system.
    • /etc/issue
    • /etc/motd
    • /etc/banner
    • /etc/ssh/banner
  2. For each file found with content remove the content, or make a backup of the file and place an empty one in it's place.
  3. After install completes successfully, it is recommended to keep the banners turned off. If required they may be turned on again.


Shared /etc/mtab file

Work with the server team to remove the shared file and update autofs configurations to only mount what is needed on these servers.