Why ntp client rejecte time server, even if time server is trusted resource?

Solution Verified - Updated -

Issue

  • Have configured two or more ntp servers. Why some of the ntp clients sync properly (adding * & + sign before servers) and some of the clients reject (do not show * or + sign) against them?
[root@example1.com]# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*192.168.2.3    128.135.14.45   2 u  118 1024  377    1.113   -0.573   0.190
 192.168.2.4    116.137.150.44   3 u  593 1024  377    1.002   39.481   0.081
 [root@example2.com]#ntpq -p
  remote           refid      st t when poll reach   delay   offset    disp
==============================================================================
*192.168.2.3    128.135.14.45   2 u  118 1024  377     1.16  -18.952    1.62
+192.168.2.4    116.137.150.44   3 u   60 1024  377     1.42   21.671    0.98

Environment

  • Red Hat Enterprise Linux 5
  • Red Hat Enterprise Linux 6
  • ntp-4.2.4
  • ntp-4.2.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.