Install or upgrade of Vertica 7, fails with error "--failure-threshold: expected one argument"

Article Id: 38578
Status: Published
Updated On: 14-02-2018 07:37
Legacy Id: TEC1422583
Products:
CA Infrastructure Management CA Infrastructure Management CA Performance Management - Usage and Administration CA Performance Management - Data Polling
Issue/Introduction:

Problem: 

When a user runs the Vertical install script (./dr_install.sh -p drinstall.properties) to freshly install or upgrade Vertica 7, the following error appears on screen and in the log file:

/opt/CA/IMDataRepository_vertica7/logs/install_log_install_<Date>_<Time>.log

e.g.:

install_log_install_12-02-2016_20-47-07.log

"

install_vertica: error: argument --failure-threshold: expected one argument

Vertica Analytic Database 7.1.2-6 Installation Tool

Installation FAILED with errors.

Installation stopped before any changes were made.

Vertica installation....................................................[FAIL]

The installation will now exit.

===============================================================================

Script finished - ./dr_install.sh

===============================================================================

"

Environment:  

CA Performance Center 2.5.0 and above

Cause: 

This is due to a known issue with the Vertica 7.0.1-2 installer and above.

If LVM is detected on any volumes (not just the volumes that Vertica uses) within the cluster, the installer will fail and stop the Vertica install script.

Workaround:

The dr_install.sh script needs to be modified to workaround this issue as per the following steps:

1. Make a backup of the original dr_install.sh file in /opt/CA/IMDataRepository_vertica7 directory

2. Use an editor to open the dr_install.sh file

3. Search for the key word "POINT_TO_POINT_SPREAD_OPTION" to find this line:

/opt/vertica/sbin/install_vertica -s $DB_HOST_NAMES -u $DB_ADMIN_LINUX_USER -l $DB_ADMIN_LINUX_USER_HOME -d $DB_DATA_DIR -L ./resources/$VLICENSE -Y -r ./resources/$VERTICA_RPM_FILE $POINT_TO_POINT_SPREAD_OPTION $failure_threshold 2>&1 | tee -a $LOG_FILE

4. In the above line, after "POINT_TO_POINT_SPREAD_OPTION", replace "$failure_threshold" and add the following new entry, surrounded by a space on each side:

--failure-threshold FAIL

The line should now appear as follows:

/opt/vertica/sbin/install_vertica -s $DB_HOST_NAMES -u $DB_ADMIN_LINUX_USER -l $DB_ADMIN_LINUX_USER_HOME -d $DB_DATA_DIR -L ./resources/$VLICENSE -Y -r ./resources/$VERTICA_RPM_FILE $POINT_TO_POINT_SPREAD_OPTION --failure-threshold FAIL 2>&1 | tee -a $LOG_FILE

5. Save the dr_install.sh file, then rerun the install script :

./dr_install.sh -p drinstall.properties

6. This time, the Vertica installation should by pass this error:

===============================================================================

Installing Data Repository (Vertica)

===============================================================================

./resources/vertica-7.1.2-6.x86_64.RHEL5.rpm located....................[OK]

./resources/vlicense.dat located........................................[OK]

Checking to see if Vertica Installation Package already exists...

Performing an upgrade of Vertica...

An existing installation was found, but /opt/vertica/config does not have expected permissions to check if the database is in an active state. The installation will continue, but may fail if an existing database is still running.

Executing an upgrade of the Vertica Installation Package...

Preparing...                ##################################################

        package vertica-7.1.2-6.x86_64 is already installed

........................................................................[OK]

Invoking install_vertica...

Vertica Analytic Database 7.1.2-6 Installation Tool

>> Validating options...

Mapping hostnames in --hosts (-s) to addresses...

        ca-xxx19                => 10.130.xxx.xxx

>> Starting installation tasks.

>> Getting system information for cluster (this may take a while)...

Default shell on nodes:

10.130.xxx.xxx /bin/bash

>> Validating software versions (rpm or deb)...

>> Beginning new cluster creation...

backing up admintools.conf on 10.130.xxx.xxx

>> Creating or validating DB Admin user/group...

Successful on hosts (1): 10.130.xxx.xxx

    Provided DB Admin account details: user = dradmin, group = verticadba, home = /export/dradmin

    Creating group... Group already exists

    Validating group... Okay

    Creating user... User already exists

    Validating user... Okay

>> Validating node and cluster prerequisites...

Failures during local (OS) configuration for verify-10.130.xxx.xxx.xml:

    HINT (S0231): https://my.vertica.com/docs/7.1.x/HTML/index.htm#cshid=S0231

        dbadmin user ('dradmin') primary group is not verticadba ('verticadba')

    HINT (S0305): https://my.vertica.com/docs/7.1.x/HTML/index.htm#cshid=S0305

        TZ is unset for dradmin. Consider updating .profile or .bashrc

    WARN (S0170): https://my.vertica.com/docs/7.1.x/HTML/index.htm#cshid=S0170

        lvscan (LVM utility) indicates some active volumes.

System prerequisites passed.  Threshold = FAIL

>> Establishing DB Admin SSH connectivity...

Installing/Repairing SSH keys for dradmin

>> Setting up each node and modifying cluster...

Creating Vertica Data Directory...

Updating agent...

Creating node node0001 definition for host 10.130.xxx.xxx

... Done

>> Sending new cluster configuration to all nodes...

>> Completing installation...

Running upgrade logic

No spread upgrade required: /opt/vertica/config/vspread.conf not found on any node

Installation complete.

Please evaluate your hardware using Vertica's validation tools:

    https://my.vertica.com/docs/7.1.x/HTML/index.htm#cshid=VALSCRIPT

To create a database:

  1. Logout and login as dradmin. (see note below)

  2. Run /opt/vertica/bin/adminTools as dradmin

  3. Select Create Database from the Configuration Menu

  Note: Installation may have made configuration changes to dradmin

  that do not take effect until the next session (logout and login).

To add or remove hosts, select Cluster Management from the Advanced Menu.

Vertica installation....................................................[OK]

===============================================================================

Create Vertica Database

===============================================================================

Creating Vertica database: da_dr on host(s): ca-xxx19 using data directory: /data and catalog directory: /catalog

Database with 1  or 2 nodes cannot be k-safe and it may lose data if it crashes

Distributing changes to cluster.

                        10.130.xxx.xxx OK [vertica][(7, 1, 2)][006][x86_64]

        Creating database da_dr

        Starting bootstrap node v_da_dr_node0001 (10.130.xxx.xxx)

        Starting nodes:

                v_da_dr_node0001 (10.130.xxx.xxx)

        Starting Vertica on all nodes. Please wait, databases with large catalogs may take a while to initialize.

        Node Status: v_da_dr_node0001: (INITIALIZING)

        Node Status: v_da_dr_node0001: (INITIALIZING)

        Node Status: v_da_dr_node0001: (UP)

Database da_dr created successfully.

........................................................................[OK]

===============================================================================

Vertica Host Configuration

===============================================================================

passwordless ssh to ca-xxx19 was successfull

Stopping vertica agent:

........................................................................[OK]

........................................................................[OK]

===============================================================================

Script finished - ./dr_install.sh

===============================================================================

Environment:

Release: IMDAGG99000-2.5-Infrastructure Management-Data Aggregator
Component: