If you want to troubleshoot why the database process is not starting, follow this checklist.
|1||Ensure Vertica is not already running on any node.
||If Vertica is not running on any nodes, go to Step 2.|
|2||Check whether the previous database shutdown was clean.
||The presence of Epoch.log indicates the shutdown was clean.
If the shutdown is clean, go to Step 3.
If the shutdown is not clean, start Vertica database. At times, you may be prompted to start Vertica at a Last Good Epoch (LGE).
|3||Check whether all the nodes are connected to each other using passwordless SSH.
||A successful connection displays last login details with date, day, and time stamp.
An unsuccessful connection prompts you for a password and displays “No route to host”.
If the connection is using passwordless SSH, go to Step 4.
If the SSH needs password, see Enable Secure Shell (SSH) Logins.
|4|| Check whether spread is communicating with all the nodes.
||If the spread is communication with other nodes, go to Step 5.
If the spread is not communicating with other nodes, see the Spread Debugging Checklist.
|5||Check whether nothing else is using/bound to the Vertica ports.
||If Vertica is bound to Vertica ports, kill all the processes holding onto Vertica ports.|
|6||Check for errors in the following locations.
||Resolve the errors in the above logs.
If you cannot resolve the error contact Vertica Technical Support with scrutinize.
|7||Check whether database process is starting after addressing the above errors, if any.
||If the database process is restarting, the checklist is complete.
If the database process is not restarting, go to Step 8.
||Please contact Vertica Technical Support.|