Vertica Fails to Start

Symptom:
capm310
Symptom:
The Data Repository does not restart after you stopped the database through Vertica admintools.
Solution:
A leap second occurred on 30 June 2015. The extra second causes Vertica to fail to start on certain versions of the Linux operating system.
To resolve this issue, restart each node before the first time you start the database.
This issue is fixed in the following Linux Kernel versions:
  • RHEL 6.1 EUS kernel-2.6.32-131.30.2 or later
  • RHEL 6.2 EUS kernel-2.6.32-220.25.1.el6 or later
  • RHEL 6.3 kernel-2.6.32-279.5.2 or later
RHEL 6.4 and later already contain a fix for this issue.