Vertica failed to start due to Leap Second and Absolute Timers Linux CAPM
search cancel

Vertica failed to start due to Leap Second and Absolute Timers Linux CAPM

book

Article ID: 4998

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration

Issue/Introduction

The US Naval Observatory announced that a leap second will be added to official timekeeping on December 31st, 2016.  The extra second will be added at 23:59:59 UTC and be denoted as 23:59:60.

Environment

CAPM 2.XOS LinuxDB Vertica

Cause

The Data Repository will not restart after you stopped the database through Vertica Admintools

Resolution

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.