My Oracle Support Banner

OL: Time Drift of 27 Seconds on Servers Syncing With Same NTP Server (Doc ID 2519831.1)

Last updated on MAY 15, 2020

Applies to:

Linux OS - Version Oracle Linux 6.0 and later
Oracle Cloud Infrastructure - Version N/A and later
Oracle Linux Cloud Service - Version Oracle Linux 6.0 and later
Linux x86-64
Linux x86-64

Symptoms

One of the servers shows a time drift of 27 seconds when compared with other servers. All the servers are synced with same NTP server.

Working Server:

# date
Tue Mar 19 18:09:37 IST 2019

Non-working Server:

# date
Tue Mar 19 18:09:10 IST 2019   <<< You can see this server is 27 seconds behind the working server.

Run "TZ=UTC date;date" on both servers.

Working Server:

# TZ=UTC date;date
Tue Mar 19 12:49:31 UTC 2019
Tue Mar 19 18:19:31 IST 2019

Non-working Server:

# TZ=UTC date;date
Tue Mar 19 12:49:06 UTC 2019
Tue Mar 19 18:18:39 IST 2019

You can see 27 seconds offset between UTC and local time on non-working server.

Working Server:

# ls -l /etc/localtime
lrwxrwxrwx. 1 root root 40 Mar 19 18:08 /etc/localtime -> ../usr/share/zoneinfo/Asia/Kolkata

# file /usr/share/zoneinfo/Asia/Kolkata
/usr/share/zoneinfo/Asia/Kolkata: timezone data, version 2, 3 gmt time flags, 3 std time flags, no leap seconds, 5 transition times, 3 abbreviation chars

Non-working Server:

# ls -l /etc/localtime
lrwxrwxrwx. 1 root root 40 Mar 19 18:08 /etc/localtime -> ../usr/share/zoneinfo/right/Asia/Kolkata

# file /usr/share/zoneinfo/right/Asia/Kolkata
/usr/share/zoneinfo/right/Asia/Kolkata: timezone data, version 2, 3 gmt time flags, 3 std time flags, 27 leap seconds, 5 transition times, 3 abbreviation chars

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.