The ntpd leap status is not reset after inserting a leap second

Solution Verified - Updated -

Issue

  • The ntpd leap status is not reset after inserting a leap second.
  • After inserting a leap second the ntpd server continues to announce an upcoming leap second.
  • Why is the leap flag(leap=01) still observed even after June 30 2015 leap second insertion in Red Hat Enterprise Linux ?

Environment

  • Red Hat Enterprise Linux 6 [ntp client and server ]
  • Red Hat Enterprise Linux 7 [ntp client and server ]
  • NTP server configured using ntp version 4.2.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content