When using ntpd, then 'leap second deletions' events are received, but not carried out by the system.

Solution Verified - Updated -


We simulated sending the LI bit(=10) from the NTP server. Ntpd on the NTP client received the LI bit(=10) (confirmed by tcpdump). The bit is not set in the kernel though, "ntpq -c rv" shows "00" in the leap field. Even after the leap second deletion time elapsed, the leap second were not deleted by the NTP client and ticked "23:59:59".


  • Red Hat Enterprise Linux (RHEL) 6 and 7
  • NTP
  • ntpd
  • leap second deletion

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