Re: [chrony-users] Fatal error : adjtimex() failed

["Tomalak Geret'kal" <tom@xxxxxxxxx>]

On 20/08/2012 22:29, Tomalak Geret'kal wrote:
> And when it *does* start up successfully, I find that 
> after some time (this varies, but on last observation was 
> around ten minutes after startup) my GPS source is being 
> selected over my PPS source (after a "no majority" event), 
> and the PPS source is apparently never selected again.
>
> Aug 20 20:35:07 sw200319 daemon.info chronyd[2098]: 
> chronyd version 1.26 starting
> Aug 20 20:35:07 sw200319 daemon.info chronyd[2098]: Linux 
> kernel major=2 minor=6 patch=21
> Aug 20 20:35:07 sw200319 daemon.info chronyd[2098]: hz=100 
> shift_hz=7 freq_scale=0.99902439 nominal_tick=10000 
> slew_delta_tick=833 max_tick_bias=1000
> Aug 20 20:35:07 sw200319 daemon.err chronyd[2098]: Could 
> not open IPv6 NTP socket : Address family not supported by 
> protocol
> Aug 20 20:35:07 sw200319 daemon.err chronyd[2098]: Could 
> not open IPv6 command socket : Address family not 
> supported by protocol
> Aug 20 20:35:07 sw200319 daemon.info chronyd[2098]: 
> Frequency -32.801 +- 0.047 ppm read from /etc/chrony.drift
> Aug 20 20:37:00 sw200319 daemon.info chronyd[2098]: 
> Selected source GPS
> Aug 20 20:37:34 sw200319 daemon.info chronyd[2098]: 
> Selected source PPS0
> [..]
> Aug 20 20:44:19 sw200319 daemon.info chronyd[2098]: Can't 
> synchronise: no majority
> Aug 20 20:45:56 sw200319 daemon.info chronyd[2098]: 
> Selected source GPS
>
> [sw200319 /root]# chronyc sources
> 210 Number of sources = 2
> MS Name/IP address           Stratum Poll LastRx Last sample
> ============================================================================ 
>
> #? PPS0                          0    4    43m  -1607ms[ 
> +400ms] +/-  155ms
> #* GPS                           0    4     16    -14ms[  
> -14ms] +/-   60ms
>
> [sw200319 /root]# cat /etc/chrony.conf
> allow
> refclock PPS /dev/pps0 lock GPS
> refclock SHM 0 offset 0.5 delay 0.1 refid GPS
> keyfile /etc/chrony.keys
> commandkey 1
> driftfile /etc/chrony.drift

Actually on review I think I can solve this particular 
sub-issue by placing the "noselect" flag on the SHM source, 
and since the PPS source is locked to it then the 
time-of-day from NMEA will still be used, if indirectly.

This is done in the example under 4.2.36 "refclock" [1], but 
I can't find it explained properly in the manual unfortunately.

Tom

[1] http://chrony.tuxfamily.org/manual.html#refclock-directive


--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.