Errors are seen installing Vertica that indicate the RPM failed to be installed

Products

• CA Infrastructure Management
• CA Performance Management

Issue/Introduction

Problem:

Receiving errors referencing RPM installation failure from Vertica when installing the Data Repository cluster.

Errors installing new Data Repository Cluster.

Errors upgrading Data Repository Cluster.

 

Errors:

The errors observed in the logs are as follows where 1.1.1.1 is NewNode01, 1.1.1.2 is NewNode02 and 1.1.1.3 is NewNode03.

Creating Vertica database: drdata on host(s): NewNode01 NewNode02 NewNode03 using data directory: /apps/CA/vertica/data and catalog directory: /apps/CA/vertica/catalog 

Distributing changes to cluster. 

1.1.1.1 OK [vertica][(7, 1, 2)][006][x86_64] 

Installation error: RPM not installed on host 1.1.1.2. 

Please verify the host is reachable and the RPM is installed.

RPM not installed on host 1.1.1.3. 

Please verify the host is reachable and the RPM is installed. 

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

 

Solution

There were two primary problems causing these failures. They are:

• Large company banners displayed by systems during user log in at the CLI
• User Security at the site

 

A large banner, displayed when a user first logs in, was enabled on all three node servers. The banner was causing the install RPM check on the remote hosts to fail. Once disabled on all there nodes the installation of Vertica was successful. 

 

While the install was successful a failure to complete the install was observed related to a problem during the DB creation stage. Further analysis showed SSH failures when using the dradmin user to run the DB creation manually via the adminTools UI. Indeed due to security restrictions the customer found the dradmin user set without access to the SSH command. Due to that, while using the root user that has those permissions to install allowed the install to complete, the dradmin user used to create the DB itself was not permitted to do so due to security restrictions that provided SSH command access to the root user, but not the dradmin OS level user.

 

Once the user was given SSH command access the DB completed its creation without error.

Environment

Release:
Component: IMSTOR