What Should I do When the Database Node is DOWN?
When database node is DOWN, troubleshoot using the following checklist.
|1||Check whether your database is UP.
||If the database is UP, go to Step 2.
If the database if not UP, restart your database.
If the database does not start, see the Database Process Not Starting checklist.
|2||Identify all the DOWN nodes.
||Upon identification of all the DOWN node/s, proceed to Step 3.|
|3||Check whether you can establish a connection with the DOWN nodes using SSH.
||If you can SSH into the node, restart Vertica process on the DOWN node.
If you cannot SSH into the node, contact your system administrator to find if it is a port issue or a network issue.
|4||To find reasons for restart failure, on the DOWN node tail startup.log. A snippet of the tail startup.log is as follows:
||The log results shows the latest state of the DOWN node. Proceed to Step 5 to see these stages.|
|5||If the startup.log…
||See the Spread Debugging Checklist.|
|b. Remains in the Recovery stage.||See the Node Recovery Checklist.|
|c. Shows an error message, Data inconsistency problems found, restart the node with the force option.
||Upon restart the checklist is complete.|
|d. Shows no new data in the startup.log after last restart, check dbLog file for errors.||If you cannot resolve errors, contact Vertica Support.|
|e. Shows Shutdown Complete but the node is still DOWN. tail vertica.log and look for <ERROR> and <PANIC>.||Contact Vertica Support with PANIC report, ErrorReport.txt, and scrutinize.|