Search Engine: Elastic

Article ID: 125888, created on Jun 16, 2015, last review on Jul 14, 2018

  • Applies to:
  • Plesk Automation


This article provides information on Plesk Automation product and leap seconds.


Leap seconds are a periodic one-second adjustment of Coordinated Universal Time(UTC) in order to keep a system's time of day close to the mean solar time. However, the Earth's rotation speed varies in response to climatic and geological events, and due to this, UTC leap seconds are irregularly spaced and unpredictable. This article seeks to provide information regarding the leap seconds themselves, along with addressing how Red Hat Enterprise Linux handles the insertion of one.

Upcoming Leap Second Events

The next leap second insertion is scheduled for June 30th, 2015 at 23:59:60 UTC.

Possible issues:

In addition, the following side-effects are possible on PA service nodes:

  1. Statistical data, which is calculated during the minute with leap second, will not contain information about events during leap second (for Windows systems);

  2. Statistical data, which is calculated during the minute with leap second, will contain double information about events during leap second (for Linux systems);

  3. Events, that take place upon determined period of time, might occur on the next period of time. For example, subscription might be expired one day later, notification might be sent on the next day, grey-listing expiration might occurs 5 minutes later.

Note: none of aforementioned effects have been confirmed or reported during the last three leap second events (in 2005, 2008, and 2012).

Additional information

#125854 [Hub] Leap second

e0aff7830fa22f92062ee4db78133079 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF