Re: [chrony-users] time sync query |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Mon, 7 Aug 2017, Jahagirdar, Bhushan wrote:
Hi,
I am using chrony stable 3.1 version.
Below is my cfg:
#For GPS data feed
refclock SOCK /var/run/chrony.ttyS1.sock poll 2 refid GPS maxsamples 4 prefer
#For CAN data feed
refclock SOCK /var/run/chrony.ttyS2.sock poll 2 delay 0.5 refid CAN maxsamples 5
No idea what CAN data feed is.
#target is one hop reachable
local stratum 1
You have this why? A refclock is stratum 0. A clock that gets its time from a
refclock is stratum 1. Why are you putting this into the confic file.
keyfile /etc/chrony/chrony.keys
makestep 0.01 -1
Below is the chrony sources o/p:
210 Number of sources = 2
.-- Source mode '^' = server, '=' = peer, '#' = local clock.
/ .- Source state '*' = current synced, '+' = combined , '-' = not combined,
| / '?' = unreachable, 'x' = time may be in error, '~' = time too variable.
|| .- xxxx [ yyyy ] +/- zzzz
|| Reachability register (octal) -. | xxxx = adjusted offset,
|| Log2(Polling interval) --. | | yyyy = measured offset,
|| \ | | zzzz = estimated error.
|| | | \
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
#? GPS 0 2 377 2 -4509h[ -4509h] +/- 6567m
#? CAN 0 2 0 - +0ns[ +0ns] +/- 0ns
My query:
Although I have given makestep 0.01 -1 and maxsample for GPS refclock is set to 4, I am still not able to see the synch
happening.
You have two sources. If there is a disagreeement chrony has no way of know
ing which is correct, making it impossible to decidee on a source.
Also what is your GPS? Is it supposed to be a PPS? They you need to have some
other source to give what second that pps refers to.
I am feeding offset data to GPS refclock for every 1 sec.
How?
Note that it says that gps is over 4000 hours out.
I think that there is something very wrong is whatever is feeding time to the
SOCK.
Can you please suggest any configuration changes here. However sometimes it works.
Similar issue I am finding in chrony 2.2 thatʼs where I thought of testing with 3.1 if this has to do with some bug.
--
Thanks and Regards,
Bhushan J.