Both nodes in a RHEL 6 High Availability cluster are rebooted after the insertion of a leap second

Solution Unverified - Updated -

Issue

  • Cluster nodes rebooted after inserting leap second. One of the nodes was evicted by the other node
        Jul  1 07:59:59 node1 kernel: Clock: inserting leap second 23:59:60 UTC
        Jul  1 08:00:14 node1 qdiskd[4889]: Writing eviction notice for node 2
        Jul  1 08:00:15 node1 qdiskd[4889]: Node 2 evicted
        Jul  1 07:59:59 node2 kernel: Clock: inserting leap second 23:59:60 UTC
        Jul  1 08:00:43 node2 kernel: imklog 5.8.10, log source = /proc/kmsg started.
        Jul  1 08:00:43 node2 rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="2144" x-info="

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with High Availability Add-On

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In