Vertica node is not starting after using -F option

Products

• Network Observability

Issue/Introduction

One of the nodes in the cluster went down, and will not start, even after using the -F opton

./admintools -t start_db -d <DB name> -F

 

Environment

PM 23.3

Cause

Passwordless SSH was not setup for the DB admin user

All nodes should have passwordless SSH between them. Otherwise any admintools commands launched from one node cannot reach the others. Cluster startup is just one example of this

Resolution

Setup passwordless SSH per the documentation

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/performance-management/23-3/administrating/data-repository-administration/configure-passwordless-ssh.html

Run the following command, on the node that is down, to start it

./admintools -t start_db -d <DB name> -F

 

 

 

Additional Information

If the node still fails to start, if it has been down for a long time, you may have to run the following command first.

Run this command from a node that is up and running; not the one that is down

select make_ahm_now('true');

Then run the following command from the node that is down

./admintools -t start_db -d <DB name> -F