Sponsored Content
Full Discussion: NTP sync problem
Operating Systems Linux Red Hat NTP sync problem Post 302370432 by uday123 on Wednesday 11th of November 2009 10:54:49 AM
Old 11-11-2009
NTP sync problem

Hi,

I have 4 machines and all are NTP configured with same ntp.conf file. But 3 machines are in sync with Time server and 4th machine is not contacting & sync with the NTP server. Please see the below details.

Code:
[root@LINUXSER01 ~]# service ntpd stop
Stopping ntpd:                                             [  OK  ]
[root@LINUXSER01 ~]# ntpdate -u NTPSERVER01
11 Nov 15:38:07 ntpdate[3010]: adjust time server 172.25.XX.XX offset -0.030428 sec
[root@LINUXSER01 ~]# service ntpd start
Starting ntpd:                                             [  OK  ]
[root@LINUXSER01 ~]# ntptime
ntp_gettime() returns code 5 (ERROR)
  time cea558ef.cbb0d000  Wed, Nov 11 2009 15:38:23.795, (.795667),
  maximum error 2064 us, estimated error 16 us
ntp_adjtime() returns code 5 (ERROR)
  modes 0x0 (),
  offset 0.000 us, frequency 0.000 ppm, interval 1 s,
  maximum error 2064 us, estimated error 16 us,
  status 0x40 (UNSYNC),
  time constant 0, precision 1.000 us, tolerance 512 ppm,
[root@LINUXSER01 ~]#


Output of ntpq -p command:
Code:
[root@LINUXSER01 ~]# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 NTPSERVER01 192.168.xxx.xxx  3 u   57   64    1    1.155  -151.64   0.002
 NTPSERVER02 192.168.xxx.xxx  3 u   56   64    1    1.245  -151.70   0.002
[root@LINUXSER01 ~]#

/etc/ntp.conf file:
Code:
restrict default kod nomodify notrap nopeer noquery
restrict 127.0.0.1
server NTPSERVER01
server NTPSERVER02
fudge   127.127.1.0 stratum 10
driftfile /var/lib/ntp/drift
keys /etc/ntp/keys
#log files
logconfig all
logfile /var/log/ntpd.log

ntpd log messages:

Code:
11 Nov 15:38:20 ntpd[3046]: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010)
11 Nov 15:38:20 ntpd[3046]: peer 172.25.xx.xx event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
11 Nov 15:38:21 ntpd[3046]: peer 192.168.xx.xx event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)

Please let me know if you need any other details to analyse the issue.
Please help me in resolving this issue.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

TIME SYNC (NTP)

Is there a utility which offers the ability to utilize NTP to sync time on machine. If so please point to man page or web site (3 Replies)
Discussion started by: SmartJuniorUnix
3 Replies

2. SuSE

unable to sync the time with ntp server

Hi folks, The server time is no tgetiing synched up with the NTP server. I tried ntpdate -u <ipadress> this is not working. please help out. regards, Sag. (7 Replies)
Discussion started by: sag71155
7 Replies

3. UNIX for Advanced & Expert Users

Sync Time/date with NTP server

Hello all, What would be the most convienint and proper way on syncing up the time and date on Solaris 8 servers with an NTP server? Any help would be appreciated. Thanks (2 Replies)
Discussion started by: Sunguy222
2 Replies

4. Solaris

NTP time sync in Solaris 10

Ok, I have 4 production systems. There is one NTP server for all four systems. In each system there is one Solaris 10 box that points to that NTP server. All of the other machines in the system point to the Solaris 10 machine to get their time sync. All four Solaris 10 machines have essentially... (2 Replies)
Discussion started by: DeCoTwc
2 Replies

5. Linux

ntp client/daemon sync

All, I need to write a script which can determine if my NTP client is X second off from the NTPD server time. I am looking for a crafty oneliner to calculate the time difference? (3 Replies)
Discussion started by: vada010
3 Replies

6. Red Hat

ntp error: time sync and frequency error

Hi Expert, One on my server keep logging this error below, how to fix this issue? Thank you. Reggy. pluton02:/home/reggy --> sudo grep "ntpd" /var/log/messages | tail Oct 6 00:26:18 pluton02 ntpd: time reset -6.588403 s Oct 6 00:26:18 pluton02 ntpd: frequency error -512 PPM exceeds... (0 Replies)
Discussion started by: regmaster
0 Replies

7. Fedora

NTP Clients not sync

hi guys I have several Red Hat 5.7(7) all of them sync time with two NTP Servers based on Windows but the issue is I configure the NTP service, I start the ntp service and use ntpdate -u to set the time the first time This is what I do 1. Configure /etc/ntp.conf restrict default kod... (2 Replies)
Discussion started by: karlochacon
2 Replies

8. Linux

Questions about the NTP time server sync

Hi folks, I have developed a Linux server for my customer. After migrating the server to my customer site, I was trying to sync its time to the NTP time servers at my customer site. Below is the ntp.conf: % vi /etc/ntp.conf # Permit time synchronization with our time source, but do not # permit... (2 Replies)
Discussion started by: kimurayuki
2 Replies

9. Solaris

Client does not sync date with ntp servers

We had a network problem a couple of days before that caused 1 interface to down and up. But today I have noticed that our date is wrong, our system have 4 servers and the other 3 are OK. I used <date> command, the result is: Fri Jan 2 17:57:55 ICT 1970 I have tried set date to be the same as... (3 Replies)
Discussion started by: salvation3103
3 Replies

10. Red Hat

Ntp client sync with local over ntp server

Hi, I have two ntp servers in my cluster and I want all the nodes in my cluster to sync with either of the ntp servers or just one. Unfortunately it keep rotating the sync, between my ntp server 1, ntp server 2 and local. Is there anyway I can change the sync to avoid local? # ntpq -p ... (3 Replies)
Discussion started by: pjeedu2247
3 Replies
ntp.drift(4)						     Kernel Interfaces Manual						      ntp.drift(4)

NAME
ntp.drift - Network Time Protocol (NTP) drift file DESCRIPTION
When the NTP daemon (xntpd) is first started, it computes the error in the intrinsic frequency of the clock on the computer it is running on. This process usually takes about a day or two after the daemon is started to compute a good estimate of this (and it needs a good estimate to synchronize closely to its server). Once the initial value is computed, it will change only by relatively small amounts during the course of continued operation. The driftfile declaration should always be included in the ntp.conf file. This provides xntpd with complete path name to a file in which it can store the current value of the frequency error. That way, if the daemon is stopped and restarted, it can reinitialize itself to the previous estimate without spending time recomputing the frequency estimate. The ntp.drift file contains one line with the following format: freq_offset flag Specifies the nominal frequency offset. DO NOT modify this field. Specifies the method used to improve system clock accuracy. Specifies that xntpd runs a Phase-Locked Loop (PLL) algorithm to keep synchronized with other hosts. This is the default. Specifies the use of the PLL algorithm in the kernel. This requires the NTP_TIME kernel option. After the option is configured in the kernel, edit the ntp.drift file and change the flag value to 1. See System Administration for information on the NTP_TIME kernel option. FILES
Conventional name of the drift file RELATED INFORMATION
Commands: ntpdate(8), ntpq(8), xntpd(8), xntpdc(8) Files: ntp.conf(4) Network Administration, System Administration delim off ntp.drift(4)
All times are GMT -4. The time now is 01:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy