When we try to start the Data Repository, either through adminTools or the CLI, the call seems to just sit there and hang without doing anything.
There is no information in the vertica.log, nor the startup.log, however, the adminTools.log shows that the node that is initiating the start call is able to connect to itself, but the calls to the other nodes never complete.
An application call Boks was inhibiting the connections from being made. Boks is a security platform used to centrally manage user identities, accounts, and privileged access, however, in this case it was disallowing full the functionality that Vertica required on startup and shutdown.
As Boks is an untested and verified application for use in conjunction with NetOps, interoperability between the two cannot be guaranteed. As such, it cannot be recommended for risk free use in conjunction with NetOps.
In this case, to retain full functionality, Boks was disabled and that allowed Vertica to start and return to full functionality.