12-11-2019
Thanks for explanation.
Quote:
ntp-serv10 # ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
*sea-gps-clock1. .GPS. 1 u 416 1024 377 1.54 -1.297 1.82
172.28.42.204 .GPS. 1 u 744 1024 0 44.45 2.298 16000.0
+172.28.34.204 .GPS. 1 u 814 1024 277 77.00 -1.162 1.37
ntp-serv10 #
ntp-serv10 # ping -s 172.28.42.204 1400 100
PING 172.28.42.204: 1400 data bytes
1408 bytes from 172.28.42.204: icmp_seq=0. time=56. ms
1408 bytes from 172.28.42.204: icmp_seq=1. time=44. ms
1408 bytes from 172.28.42.204: icmp_seq=2. time=45. ms
1408 bytes from 172.28.42.204: icmp_seq=3. time=44. ms
1408 bytes from 172.28.42.204: icmp_seq=4. time=44. ms
1408 bytes from 172.28.42.204: icmp_seq=5. time=45. ms
^C
----172.28.42.204 PING Statistics----
6 packets transmitted, 6 packets received, 0% packet loss
round-trip (ms) min/avg/max = 44/46/56
ntp-serv10 #
Here is my current conf file :
Quote:
ntp-serv10 # cat /etc/inet/ntp.conf | grep -v "#"
server 192.168.70.16 prefer
server 172.28.42.204
server 172.28.34.204
driftfile /var/ntp/ntp.drift
statsdir /var/ntp/ntpstats/
filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
filegen clockstats file clockstats type day enable
How will I explain, if synchronisation is being lost to all these devices? Is it dragging back by (approx) 1 second? I see these messages for today morning too
Quote:
ntp-serv10 # cat /var/adm/messages | grep ntp | tail -10
Dec 9 13:13:15 ntp-serv10 xntpd[15247]: [ID 854739 daemon.info] synchronized to 172.28.34.204, stratum=1
Dec 9 13:13:14 ntp-serv10 xntpd[15247]: [ID 774427 daemon.notice] time reset (step) -1.003379 s
Dec 9 13:13:14 ntp-serv10 xntpd[15247]: [ID 204180 daemon.info] synchronisation lost
Dec 9 13:17:34 ntp-serv10 xntpd[15247]: [ID 854739 daemon.info] synchronized to 192.168.70.16, stratum=1
Dec 11 06:19:58 ntp-serv10 xntpd[15247]: [ID 774427 daemon.notice] time reset (step) 0.999029 s
Dec 11 06:19:58 ntp-serv10 xntpd[15247]: [ID 204180 daemon.info] synchronisation lost
Dec 11 06:24:58 ntp-serv10 xntpd[15247]: [ID 854739 daemon.info] synchronized to 192.168.70.16, stratum=1
Dec 11 06:24:57 ntp-serv10 xntpd[15247]: [ID 774427 daemon.notice] time reset (step) -1.003025 s
Dec 11 06:24:57 ntp-serv10 xntpd[15247]: [ID 204180 daemon.info] synchronisation lost
Dec 11 06:30:18 ntp-serv10 xntpd[15247]: [ID 854739 daemon.info] synchronized to 192.168.70.16, stratum=1
ntp-serv10 #
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi Friends,
How can I Restore the Files present under "lost+found" Directory of a FileSystem (in Solaris & Tru64 OS) to their original Locations.
Now-a-days I am loosing lots of files in 2 of my Machines,
One running Solaris8 and other Tru64(Digital) Unix.
Thanx in... (1 Reply)
Discussion started by: dhasarath
1 Replies
2. UNIX for Dummies Questions & Answers
Is there some way to force the NTP server on a brand-new install to be "suitable" to sync other servers from? (I'm more concerned with synchronization between machines, and less concerned with what the actual time they sync to is)
For example, whenever I install fresh from the Fedora DVDs and... (0 Replies)
Discussion started by: jjinno
0 Replies
3. Linux
does anyone know how to change the treshold of 128ms in NTP.
in order to ignore these alarms:
Oct 27 14:44:15 rt1 ntpd: synchronisation lost
Oct 27 15:08:25 rt1 ntpd: time reset 0.688591 s
Oct 27 15:08:25 rt1 ntpd: synchronisation lost
Oct 27 15:28:45 rt1 ntpd: time reset 0.462257 s (0 Replies)
Discussion started by: modcan
0 Replies
4. UNIX for Advanced & Expert Users
Hi,
I was trying to call "script <an ip add>" command from .profile file to log everything whenever anyone logs in to this user. I did the following at the end of .profile. 1) Extracted the IP address who logged in 2) Called script < ip add> . The problem I am facing is all, aliases etc. written... (3 Replies)
Discussion started by: amicon007
3 Replies
5. AIX
Hi,
This is odd, however here goes. There are several shell scripts that run in our production environment AIX 595 LPAR m/c, which has sufficient memory 14GB (physical memory) and horsepower 5CPUs. However from time to time we get the following errors in these shell scripts. The time when these... (11 Replies)
Discussion started by: jerardfjay
11 Replies
6. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
7. Solaris
Need to find a way to import an LP printers.conf file to CUPS. I have some new Solaris 11.1 boxes that need to have 300 printers added. (0 Replies)
Discussion started by: os2mac
0 Replies
8. UNIX for Dummies Questions & Answers
Hi All,
I'm completely new to bash scripting and still learning my way through albeit vey slowly.
I need to know where to insert my server names', my ip address numbers through out the script alas to no avail.
I'm also searching on how to save .sh (bash shell) script properly.... (25 Replies)
Discussion started by: profileuser
25 Replies
9. Shell Programming and Scripting
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
LEARN ABOUT DEBIAN
radioclkd
RADIOCLKD(1) Network Time Protocol Daemon RADIOCLKD(1)
NAME
radioclkd - decode time from radio clock(s) attached to serial port
SYNOPSIS
radioclkd [ -tphv ] device
DESCRIPTION
radioclkd is a simple daemon that decodes the time from a radio clock device attached to the DCD and/or CTS and/or DSR status lines of
serial port of a computer. It is able to decode the DCF77, MSF and WWVB time signals. The received time is then sent to ntpd using the
shared memory reference clock driver. The type of time signal being received is automatically determined. If you have problems getting the
program to work using interrupts, the following command is known to help in many instances. If this fails you can always fall back to the
polling method.
stty crtscts < /dev/ttyS0
Details on a cheap and easy to make device for receiving these time signals can be found at
http://www.buzzard.org.uk/jonathan/radioclock.html
OPTIONS
-p, --poll
Poll the serial port for changes of status in the DCD, CTS and DSR lines rather than use interrupts
-t, --test
Enter test mode printing the length of each pulse and the decoded time at the end of each minute on stdout. The time is not sent to
ntpd using the shared memory reference clock driver in this mode.
-h, --help
Print a short synopsis of the command line arguments.
-v, --version
Print the version number and then exit.
CONFIGURATION
Configuration is very simple. Use server 127.127.28.0 in your ntp.conf file for a clock attached to the DCD line, server 127.127.28.1 for a
clock attached to the CTS line, and server 127.127.28.2 for a clock attached to the DSR line. You will also want to use a fudge line on the
server to change the displayed refid.
CALIBRATION
Due to delays in the propogation of the radio signal, it's processing by the receiver board and the latency of the operating system the
time decoded by the receiver will be slightly offset from actual UTC. Typically this delay will be less than 20ms, so unless you are very
fussy about the time, or are using more than one time source, such as a GPS unit, other radio clock or NTP server on the internet you can
ignore this section.
The basics of the calibration procedure is to determine the average offset of the radio receiver, and use the time1 fudge factor in
ntp.conf to bring the receiver as close as possible to the real time. The easiest way of determining the offset of the radio receivers time
is to run it against a reference clock that does not suffer from these problems. The best reference clock would be a GPS unit. This might
be a GPS unit that you don't wish to dedicate to time keeping, or a borrowed unit. If this is not possible you could use a stratum 1 server
on the internet.
The method of calibration is quite simple. We attach the calibration reference clock to the computer and fudge the stratum of our radio
receiver up to say 5. This way we can be sure that ntpd will lock onto the calibration reference clock. We need to make sure that ntpd is
configured to collect peer statistics so make sure we have some lines similar to these in ntp.conf
statsdir /var/log/ntpstats/
statistics loopstats peerstats clockstats
filegen peerstats file peerstats type day enable
After that we restart ntpd and leave it running for several hours. We can then make a copy the peerstats file. The trick is to remove all
the entries before ntpd has come into close aggrement with the calibration reference clock and then run the peer.awk script in the
scripts/stats directory of the ntp distribution. This will give us a mean offset of our radio receivers in milliseconds. This can them be
converted into seconds and added to the fudge line in ntp.conf for our receiver.
The final step is to remove the change in stratum level for our reference clock and restart ntpd. If you move the receiver any significant
distance then you will need to repeat this calibration step. Across the room or around the current building will be fine, but if you move
it to the next town/city then you will need to recalibrate.
IN USE
The version of ntpd that comes with most Linux distributions does not have the shared memory reference clock driver compiled in by default.
This can be identified by checking the logs after ntpd is started. If the shared memory reference clock driver is not compiled in then the
logs will contain warnings about the reference clock driver not being recognized. To compile ntpd with the shared memory reference clock
driver you must specify the --enable-SHM option when running configure.
Neither radioclkd or ntpd ever mark the shared memory segment for deletion. If you stop using the shared memory reference clock driver
therefore any shared memory segments will persist until you reboot or manually delete the segment using ipcrm. The segments can be identi-
fied as the one with key 0x4e545030, 0x4e545031 or 0x4e545032 using the ipcs command.
BUGS
If you are running a kernel with the PPS kit and have a clock attached to the DCD line you may experience lockups. If you encounter this
problem the currently recomended solution is to move the clock to either the CTS or DSR lines.
AUTHOR
This program was written by Jonathan Buzzard <jonathan@buzzard.org.uk> and may be freely distributed under the terms of the GNU General
Public License. There is ABSOLUTELY NO WARRANTY for this program.
Version 1.0 19 Jan 2003 RADIOCLKD(1)