|Re: [chrony-users] Fatal error : adjtimex() failed|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
On 20/08/2012 18:49, Tomalak Geret'kal wrote:
Now the problem has evolved, without changing the chrony
binary or configuration:
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 needs.
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
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?
Fatal error : shmget() failed
At this point I decided to (a) run chronyd with the "-d"
switch so I could see source file and line numbers in the
error output, and (b) add some additional diagnostics to the
messages that I was seeing.
refclock_shm.c:71:(shm_initialise)[20-19:42:16] Fatal error
: shmget(1314148400,80,896) failed, errno: 2 (No such file
Now this is strange since a separate program of mine that
gets the same SHM segment at the same address with the same
parameters succeeds as it always has done. Both run as root.
Starting to suspect some strange tomfoolery elsewhere on the
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.