Package: chrony
Version: 1.23-6
Severity: important
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hello,
I've just noticed that one of my systems had its clock out of sync with
that of the timeserver. The timeserver is another Debian machine running
chrony (also version 1.23-6). On investigation, it seems that chronyd
had been started, but then exited on segfault soon after.
I started running through the steps that /etc/init.d/chrony would run
through when given the "start" parameter, and found that for my system,
the problem was completely reproducible. The segfault always occurred
after chronyc processed the "burst 5/10" command, as requested by
chrony's init script.
A simple workaround for this problem, as it isn't needed for my purposes,
is simply not to get chronyc to send this command. I've included a patch
to the init script to illustrate the point, and in case it is of any use,
a copy of my chrony.conf. If you'd like any further information, feel
free to get in touch and I'll add more information to the bug report as
soon as possible.
All the best,
- -Dave.
- -- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.27.4 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages chrony depends on:
ii libc6 2.9-4 GNU C Library: Shared libraries
ii libreadline5 5.2-3.1 GNU readline and history libraries
ii timelimit 1.4-1 Simple utility to limit a process'
ii ucf 3.0016 Update Configuration File: preserv
Versions of packages chrony recommends:
ii udev 0.125-7 /dev/ and hotplug management daemo
chrony suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iQIcBAEBCgAGBQJJsC7qAAoJEBIA1yCB7VsR998P/3/dK6aP3BmaAhPY6+6p1gsH
ZuVNYTTIi3v3RozBi4dvf2N82Zg3AbWapwVSchpSaw8JQHgUN6+AacLv77ti5Gzs
T0ehHaE9CIl+gMyqIVFHKZN2R09w3cs56zBQm/2z2br1u6bzwsRU6isI4RW645Hc
8BT10dwmRhTIiE6Yb5V7M9fe1xxKLsw9QoQdwyVVfOOX4mLb7zXHhLg5nEz3Phqg
g9ZvNQX3r2zd4GWUUzaQm7HOtWnmlUXUOboHtpng3FmlLhPcwr1iuKNaAO23XxI5
x6qv5kXwgfMHCswV4nHAPAgVyZnFkQmSWuWs86eMp8bIhzQnEbatwwH1EmqqN7JT
+LA6iAKNiBGL7XK69VTSE2tVXK0P51eNheXS1Vb6gV+aVt1CvzB1MSwY57DoP806
ijy2j1966Da2zeWJkT63HgeYmg/IekYlMZyQ+aAVyKaaIiTSDLa1MOhA1wa33w5J
MUojK4F/yspv29md1UveQG8OVuT/GrgjlRcw0jqT08H7TE0zWe33W7MkHctSivHV
XY0A8uPlEHkCRKJQH+zy2bgIbCHln1wozTj5LA8MRMwr9YV8nYKVNCO9iw/7Dwu2
Nbr77WY19SZdF82ZP5XRm6S6EDDf+rAQCu5zNEDitNkJS4vKEAz/yEirousR644I
TOWAe8s9n0KmNQga8UJm
=x0Qb
-----END PGP SIGNATURE-----
--- /etc/init.d/chrony.orig 2009-03-05 19:48:37.000000000 +0000
+++ /etc/init.d/chrony 2009-03-05 19:49:00.000000000 +0000
@@ -36,7 +36,6 @@
if timelimit -q -s9 -t5 -- /usr/bin/chronyc > /dev/null << EOF
password $PASSWORD
online
-burst 5/10
quit
EOF
then
server ntp.winterwolf.co.uk
driftfile /etc/chrony.drift
#rtcfile /etc/chrony.rtc
keyfile /etc/chrony/chrony.keys
commandkey 1
cmdport 323
initstepslew 02 ntp.winterwolf.co.uk
logchange 2.0
mailonchange [email protected] 5.0
