• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 125848, created on Jun 11, 2015, last review on Jun 19, 2015

Purpose

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

Introduction

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:

Note: No issues have been reported regarding leap second and its influence on Plesk during the last three leap second events on 2005, 2008, and 2012.

Based on the current experience, leap second would not affect Plesk.

Possible side-effects are:

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

  2. Statistical data which is calculated during the minute with the leap second will contain double information about the events which occurred during the 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 expire one day later, notification might be sent on the next day, grey-listing expiration might occur with a 5 minute delay.

All Plesk services are connected with the system time - that is why they will grab the new time automatically. Therefore it is recommended to explore known issues regarding the leap second for a particular operating system.

Additional information

#125854 [Hub] Leap second

a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 0efe2234e2ce513f2186f26c68447702

Email subscription for changes to this article
Save as PDF