Hi,

On all my Linux machines . My time is increasing by 27 secs. I am using public NTP server. As per logs my time is increasing by 27 sec. I am showing below logs + ntp.conf

Apr 11 03:27:58 test_comp ntpd[19193]: kernel time sync status 0040
Apr 11 03:27:59 test_comp ntpd[19193]: kernel time sync disabled 0001
Apr 11 05:28:40 test_comp ntpd[21967]: kernel time sync status 0040
Apr 11 05:29:09 test_comp ntpd[21967]: time reset +27.666479 s
Apr 11 05:29:09 test_comp ntpd[21967]: kernel time sync disabled 0001
Apr 11 05:32:22 test_comp ntpd[24121]: kernel time sync status 0040
Apr 11 05:32:24 test_comp ntpd_initres[24123]: host name not found: time.microsoft.com
Apr 11 05:32:24 test_comp ntpd_initres[24123]: couldn't resolve `time.microsoft.com', giving up on it
Apr 11 05:33:56 test_comp ntpd[24958]: kernel time sync status 0040
Apr 11 05:33:57 test_comp ntpd[24958]: kernel time sync enabled 0001


cat /etc/ntp.conf

# Permit all access over the loopback interface. This could
# be tightened as well, but to do so would effect some of
# the administrative functions.
restrict 127.0.0.1
restrict -6 ::1

# Hosts on local network are less restricted.
#restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap

# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
server time.windows.com
#server pool.ntp.org
#server 0.rhel.pool.ntp.org
#server 1.rhel.pool.ntp.org
#server 2.rhel.pool.ntp.org

#broadcast 192.168.1.255 key 42 # broadcast server
#broadcastclient # broadcast client
#broadcast 224.0.1.1 key 42 # multicast server
#multicastclient 224.0.1.1 # multicast client
#manycastserver 239.255.254.254 # manycast server
#manycastclient 239.255.254.254 key 42 # manycast client

# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available.
#server 127.127.1.0 # local clock
#fudge 127.127.1.0 stratum 10

# Drift file. Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
driftfile /var/lib/ntp/drift

# Key file containing the keys and key identifiers used when operating
# with symmetric key cryptography.
keys /etc/ntp/keys

# Specify the key identifiers which are trusted.
#trustedkey 4 8 42

# Specify the key identifier to use with the ntpdc utility.
#requestkey 8

# Specify the key identifier to use with the ntpq utility.
#controlkey 8


tos maxdist 100000000000000000


# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*wwwco1test16.mi 129.6.15.28 2 u 223 512 377 75.249 -5.604 5.633

Thanks,

My question is why 27 Seconds were exceeding and it happened on all machines. Is it because of time server issue ? How can i proove.

Apr 11 05:29:09 test_comp ntpd[21967]: time reset +27.666479 s

Are these physical or virtual machines.

Why are you using the windows time server versus the Redhat pool or at least a pool that is close to your location.

It is physical box. I was using the local time server that moment. it was the same problem I was facing while using local NTP server. Then i chose this windows NTP server on that machine temporarily . but again it added 27 seconds. why these 27 secs were adding on all my Linux machines only. Below were the results of two other machines machines. all machines were adding 27 sec. Is it problem with NTP server at any time. Because i asked to windows team they said all windows machines have correct time. Can you plz give me the reason of lagging on linux machines only?


remote refid st t when poll reach delay offset jitter
==============================================================================
*NTP server. 1 u 12 64 367 0.401 -14.025 7.730

remote refid st t when poll reach delay offset jitter
==============================================================================
*NTP server. 1 u 686 1024 377 0.414 8.264 0.530

What happens when you go back to using the RHEL pool?
Explain what you are using for the local NTP server?

Hey I'm curious. Does this 27-second reset happen only once a day? And only on a specific time server correct?

I wonder if somehow there's another thing that makes your system update back to the time which is 27 seconds late from the time servers.

it happened only once at that time.