Sponsored Content
Top Forums UNIX for Dummies Questions & Answers NTP high offset | no servers can be used, exiting Post 302839413 by rbatte1 on Thursday 1st of August 2013 12:58:44 PM
Old 08-01-2013
I think that you would be far better getting the time sources that you will be relying on into step first, else you will never know where you are.

Imagine that you get your time from NTPserver1 and that has no connection to NTPserver2 and they drift apart. Now you will need to consider which is the correct one and which clients refer to which. Worse still, if your NTPserver1 drops and you automatically detect and use the time from NTPserver2, you could see a dramatic and unplanned time step, perhaps even moving the clock backwards by several minutes and that could be devastating to any applications of schedulers that rely on accurate time.

Basically, you need to:-
  1. Get your time servers agreeing on what your company standard time is first and keeping in sync with each other (and perhaps an internet or radio source)
  2. Use ntpdate to step your server into line with any of them - pick a quiet time to do this.
  3. Start your NTP client (ntpd or xntpd usually) to keep in sync with them.


I hope that this helps.


Robin
Liverpool/Blackburn
UK
 

9 More Discussions You Might Find Interesting

1. Solaris

ntp server and ntp client

All, How do you set a Solaris 9 server which received ntp updates from a ntp server to broadcast them on a local subnet. I have created a /etc/inet/ntp.conf file to receive the updates from a server on network and need to make this server become like a ntp relay from the main server. Any... (1 Reply)
Discussion started by: bubba112557
1 Replies

2. UNIX for Dummies Questions & Answers

How to setup NTP on unix and linux servers?

I have a hostname/ip of our network time server. What are the steps to take to set each server up to synchronize the clocks? Thanks (4 Replies)
Discussion started by: ChadKam
4 Replies

3. AIX

Configure one host against two ntp servers for redundancy

Dears all is it possible to have two NTP servers in one host ? how i can configure them . please advice (5 Replies)
Discussion started by: thecobra151
5 Replies

4. Solaris

NTP client offset

How to add offset to NTP client so that, for eg., clock is -20 seconds? (2 Replies)
Discussion started by: orange47
2 Replies

5. HP-UX

Setting up NTP HP-UX clients from solaris NTP server

Hi I wonder if its possible to setup NTP clients running HP-UX o.s. from a solaris 10 NTP server? FR (3 Replies)
Discussion started by: fretagi
3 Replies

6. 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

7. UNIX for Advanced & Expert Users

Grep --byte-offset not returning the offset (Grep version 2.5.1)

Hi, I am trying to get the position of a repeated string in a line using grep -b -o "pattern" In my server I am using GNU grep version 2.14 and the code is working fine. However when I am deploying the same code in a different server which is using GNU grep version 2.5.1 the code is not... (3 Replies)
Discussion started by: Subhamoy
3 Replies

8. 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

9. Shell Programming and Scripting

High availability of a process between two Linux servers

Hello, I would like to create a script that will maintain HA/failover of a process between two servers. I wanted to send a continuous heartbeat message through a script to another server when everything is working fine, if a process has gone down then the same message should be sent another... (4 Replies)
Discussion started by: Mahesh_RPM
4 Replies
ntpdate(8)						      System Manager's Manual							ntpdate(8)

NAME
ntpdate - set the date and time via NTP Disclaimer: The functionality of this program is now available in the ntpd program. See the -q command line option in the ntpd - Network Time Protocol (NTP) daemon page. After a suitable period of mourning, the ntpdate program is to be retired from this distribution SYNOPSIS
ntpdate [ -46bBdqsuv ] [ -a key ] [ -e authdelay ] [ -k keyfile ] [ -o version ] [ -p samples ] [ -t timeout ] [ -U user_name ] server [ ... ] DESCRIPTION
ntpdate sets the local date and time by polling the Network Time Protocol (NTP) server(s) given as the server arguments to determine the correct time. It must be run as root on the local host. A number of samples are obtained from each of the servers specified and a subset of the NTP clock filter and selection algorithms are applied to select the best of these. Note that the accuracy and reliability of ntpdate depends on the number of servers, the number of polls each time it is run and the interval between runs. ntpdate can be run manually as necessary to set the host clock, or it can be run from the host startup script to set the clock at boot time. This is useful in some cases to set the clock initially before starting the NTP daemon ntpd. It is also possible to run ntpdate from a cron script. However, it is important to note that ntpdate with contrived cron scripts is no substitute for the NTP daemon, which uses sophisticated algorithms to maximize accuracy and reliability while minimizing resource use. Finally, since ntpdate does not discipline the host clock frequency as does ntpd, the accuracy using ntpdate is limited. Time adjustments are made by ntpdate in one of two ways. If ntpdate determines the clock is in error more than 0.5 second it will simply step the time by calling the system settimeofday() routine. If the error is less than 0.5 seconds, it will slew the time by calling the system adjtime() routine. The latter technique is less disruptive and more accurate when the error is small, and works quite well when ntp- date is run by cron every hour or two. ntpdate will decline to set the date if an NTP server daemon (e.g., ntpd) is running on the same host. When running ntpdate on a regular basis from cron as an alternative to running a daemon, doing so once every hour or two will result in precise enough timekeeping to avoid stepping the clock. Note that in contexts where a host name is expected, a -4 qualifier preceding the host name forces DNS resolution to the IPv4 namespace, while a -6 qualifier forces DNS resolution to the IPv6 namespace. If NetInfo support is compiled into ntpdate, then the server argument is optional if ntpdate can find a time server in the NetInfo configu- ration for ntpd. COMMAND LINE OPTIONS
-4 Force DNS resolution of following host names on the command line to the IPv4 namespace. -6 Force DNS resolution of following host names on the command line to the IPv6 namespace. -a key Enable the authentication function and specify the key identifier to be used for authentication as the argument key. The keys and key identifiers must match in both the client and server key files. The default is to disable the authentication function. -B Force the time to always be slewed using the adjtime() system call, even if the measured offset is greater than +-500 ms. The default is to step the time using settimeofday() if the offset is greater than +-500 ms. Note that, if the offset is much greater than +-500 ms in this case, that it can take a long time (hours) to slew the clock to the correct value. During this time. the host should not be used to synchronize clients. -b Force the time to be stepped using the settimeofday() system call, rather than slewed (default) using the adjtime() system call. This option should be used when called from a startup file at boot time. -d Enable the debugging mode, in which ntpdate will go through all the steps, but not adjust the local clock. Information useful for general debugging will also be printed. -e authdelay Specify the processing delay to perform an authentication function as the value authdelay, in seconds and fraction (see ntpd for details). This number is usually small enough to be negligible for most purposes, though specifying a value may improve timekeeping on very slow CPU's. -k keyfile Specify the path for the authentication key file as the string keyfile. The default is /etc/ntp/keys. This file should be in the format described in ntpd. -o version Specify the NTP version for outgoing packets as the integer version, which can be 1 or 2. The default is 4. This allows ntpdate to be used with older NTP versions. -p samples Specify the number of samples to be acquired from each server as the integer samples, with values from 1 to 8 inclusive. The default is 4. -q Query only - don't set the clock. -s Divert logging output from the standard output (default) to the system syslog facility. This is designed primarily for convenience of cron scripts. -t timeout Specify the maximum time waiting for a server response as the value timeout, in seconds and fraction. The value is is rounded to a multiple of 0.2 seconds. The default is 1 second, a value suitable for polling across a LAN. -u Direct ntpdate to use an unprivileged port for outgoing packets. This is most useful when behind a firewall that blocks incoming traffic to privileged ports, and you want to synchronize with hosts beyond the firewall. Note that the -d option always uses unprivileged ports. -v Be verbose. This option will cause ntpdate's version identification string to be logged. -U user_name ntpdate process drops root privileges and changes user ID to user_name and group ID to the primary group of server_user. DIAGNOSTICS
ntpdate's exit status is zero if it finds a server and updates the clock, and nonzero otherwise. FILES
/etc/ntp/keys - encryption keys used by ntpdate. BUGS
The slew adjustment is actually 50% larger than the measured offset, since this (it is argued) will tend to keep a badly drifting clock more accurate. This is probably not a good idea and may cause a troubling hunt for some values of the kernel variables tick and tickadj. SEE ALSO
ntpd(8) The official HTML documentation. This file was automatically generated from HTML source. ntpdate(8)
All times are GMT -4. The time now is 08:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy