|[chrony-users] Fatal error : adjtimex() failed|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
I'm replacing ntpd with chronyd on a busybox-driven Linux
2.6.21 ARM device that takes time from a local GPS receiver
with PPS and/or remote NTP servers. We've never been able to
get ntpd working with the ATOM PPS driver and we have some
fiddly time-step requirements that led us to decide that a
timepps-enabled chrony build would be more suitable for our
But, after an hour or so of lovely NMEA and PPS -steered
time, for reasons unknown I'm no longer able to get chrony
to even run.
In the syslog:
Aug 20 17:32:50 sw200319 daemon.info chronyd: chronyd version 1.26 starting
Aug 20 17:32:50 sw200319 daemon.info chronyd: Linux kernel major=2 minor=6 patch=21
Aug 20 17:32:50 sw200319 daemon.info chronyd: hz=100 shift_hz=7 freq_scale=0.99902439 nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000
Aug 20 17:32:50 sw200319 daemon.crit chronyd: Fatal error : adjtimex() failed
I read that adjtimex() can fail when the HZ and SHIFT_HZ
values are incorrect, but I checked the source for our
kernel and in it HZ is set at100. I tried "linux_hz 1000"
for good measure, with no effect.
I power-cycled the device, with no effect.
refclock PPS /dev/pps0 lock GPS
refclock SHM 0 offset 0.5 delay 0.1 refid GPS
and removing more or less any of these entries doesn't
appear to make a difference.
What else might I be missing?
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.