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
NTPD(8) 					   The Network Time Protocol (NTP) Distribution 					   NTPD(8)

NAME
ntpd - Network Time Protocol (NTP) daemon SYNOPSIS
ntpd [ -46aAbgLmnNqx ] [ -c conffile ] [ -f driftfile ] [ -i jaildir ] [ -k keyfile ] [ -l logfile ] [ -p pidfile ] [ -P priority ] [ -r broadcastdelay ] [ -s statsdir ] [ -t key ] [ -u user[:group] ] [ -U interface_update_interval ] [ -v variable ] [ -V variable ] DESCRIPTION
The ntpd program is an operating system daemon which sets and maintains the system time of day in synchronism with Internet standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but also retains compatibility with version 3, as defined by RFC-1305, and version 1 and 2, as defined by RFC-1059 and RFC-1119, respectively. ntpd does most computations in 64-bit float- ing-point arithmetic and does relatively clumsy 64-bit fixed-point operations only when necessary to preserve the ultimate precision, about 232 picoseconds. While the ultimate precision is not achievable with ordinary workstations and networks of today, it may be required with future gigahertz CPU clocks and gigabit LANs. The daemon can operate in any of several modes, including symmetric active/passive, client/server broadcast/multicast and manycast. A broadcast/multicast or manycast client can discover remote servers, compute server-client propagation delay correction factors and config- ure itself automatically. This makes it possible to deploy a fleet of workstations without specifying configuration details specific to the local environment. Ordinarily, ntpd reads the ntp.conf configuration file at startup time in order to determine the synchronization sources and operating modes. It is also possible to specify a working, although limited configuration entirely on the command line, obviating the need for a configuration file. This may be particularly appropriate when the local host is to be configured as a broadcast/multicast client or many- cast client, with all peers being determined by listening to broadcasts at run time. Various internal ntpd variables can be displayed and configuration options altered while the daemon is running using the ntpq and ntpd utility programs. When ntpd starts it looks at the value of umask, and if it is zero ntpd will set the umask to 0222. OPTIONS
-a Require cryptographic authentication for broadcast client, multicast client and symmetric passive associations. This is the default. -A Do not require cryptographic authentication for broadcast client, multicast client and symmetric passive associations. This is almost never a good idea. -b Enable the client to synchronize to broadcast servers. -c conffile Specify the name and path of the configuration file, default /etc/ntp.conf. -f driftfile Specify the name and path of the frequency file, default /etc/ntp.drift. This is the same operation as the driftfile driftfile con- figuration command. -g Normally, ntpd exits with a message to the system log if the offset exceeds the panic threshold, which is 1000 s by default. This option allows the time to be set to any value without restriction; however, this can happen only once. If the threshold is exceeded after that, ntpd will exit with a message to the system log. This option can be used with the -q and -x options. -i jaildir Chroot the server to the directory jaildir. This option also implies that the server attempts to drop root privileges at startup (otherwise, chroot gives very little additional security). You may need to also specify a -u option. -I [address | interface name] Open the network address given, or all the addresses associated with the given interface name. This option may appear multiple times. This option also implies not opening other addresses, except wildcard and localhost. This option is deprecated. Please consider using the configuration file interface command, which is more versatile. -k keyfile Specify the name and path of the symmetric key file, default /etc/ntp.keys. This is the same operation as the keys keyfile configu- ration command. -l logfile Specify the name and path of the log file. The default is the system log file. This is the same operation as the logfile logfile configuration command. -L Do not listen to virtual IPs. The default is to listen. -n Don't fork. -N To the extent permitted by the operating system, run the ntpd at the highest priority. -p pidfile Specify the name and path of the file used to record the ntpd process ID. This is the same operation as the pidfile pidfile config- uration command. -P priority To the extent permitted by the operating system, run the ntpd at the specified priority. -q Exit the ntpd just after the first time the clock is set. This behavior mimics that of the ntpdate program, which is to be retired. The -g and -x options can be used with this option. Note: The kernel time discipline is disabled with this option. -r broadcastdelay Specify the default propagation delay from the broadcast/multicast server to this client. This is necessary only if the delay can- not be computed automatically by the protocol. -s statsdir Specify the directory path for files created by the statistics facility. This is the same operation as the statsdir statsdir con- figuration command. -t key Add a key number to the trusted key list. This option can occur more than once. -u user[:group] Specify a user, and optionally a group, to switch to. -U interface_update_interval Number of seconds to wait between interface list scans to pick up new and delete network interface. Set to 0 to disable dynamic interface list updating. The default is to scan every 5 minutes. -v variable, -V variable Add a system variable listed by default. -x Normally, the time is slewed if the offset is less than the step threshold, which is 128 ms by default, and stepped if above the threshold. This option sets the threshold to 600 s, which is well within the accuracy window to set the clock manually. Note: Since the slew rate of typical Unix kernels is limited to 0.5 ms/s, each second of adjustment requires an amortization interval of 2000 s. Thus, an adjustment as much as 600 s will take almost 14 days to complete. This option can be used with the -g and -q options. Note: The kernel time discipline is disabled with this option. FILES
/etc/ntp.conf default name of the configuration file /etc/ntp.drift default name of the drift file SEE ALSO
ntp.conf(5), ntpdate(8) The complete documentation can be found at /usr/share/doc/ntp-doc/html/ntpd.html in the package ntp-doc. Debian 2007-12-07 NTPD(8)
All times are GMT -4. The time now is 12:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy