Your message dated Mon, 02 Jul 2012 23:17:10 +0000
with message-id <[email protected]>
and subject line Bug#518385: fixed in chrony 1.26-2
has caused the Debian Bug report #518385,
regarding Chrony segfaults on startup (narrowed down to chronyc and "burst")
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
518385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518385
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: chrony
Source-Version: 1.26-2
We believe that the bug you reported is fixed in the latest version of
chrony, which is due to be installed in the Debian FTP archive:
chrony_1.26-2.diff.gz
to main/c/chrony/chrony_1.26-2.diff.gz
chrony_1.26-2.dsc
to main/c/chrony/chrony_1.26-2.dsc
chrony_1.26-2_amd64.deb
to main/c/chrony/chrony_1.26-2_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
John G. Hasler <[email protected]> (supplier of updated chrony package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 01 Jul 2012 22:05:56 -0500
Source: chrony
Binary: chrony
Architecture: source amd64
Version: 1.26-2
Distribution: unstable
Urgency: low
Maintainer: John G. Hasler <[email protected]>
Changed-By: John G. Hasler <[email protected]>
Description:
chrony - Sets your computer's clock from time servers on the Net
Closes: 195620 294030 407466 479389 518385 655123
Changes:
chrony (1.26-2) unstable; urgency=low
.
* Fixed Makefile.in so that getdate.c gets made (and removed
in "clean"). This will go upstream. Moved faq stuff in rules
from binary-indep to binary-arch.
* Restored accidently deleted nmu changelog entry.
.
* Applied patch from Moritz Muehlenhoff <[email protected]>
Closes: #655123 Please enabled hardened build flags
.
* Fixed upstream.
Closes: #518385 Chrony segfaults on startup (narrowed down to
chronyc and "burst")
.
* Added DEB_BUILD_OPTIONS=noopt to rules.
Added build-arch and build-indep to rules.
Prefix is now 'usr'.
Changed to dh_installman.
Fixed "clean:" target.
Closes: #479389 Improvements for debian/rules
.
* Fixed upstream.
Closes: #195620 Strange "System time : xxx seconds slow of NTP time"
output
.
* Upstream changes should have fixed this.
Closes:#294030 chronyd makes the whole system briefly (< 1 second)
freeze
.
* Fixed by upstream changes and new LSB headers.
Closes: #407466 Chrony won't access hardware clock but prevents
hwclock from doing so either
Checksums-Sha1:
562533aa4681792df3d056a6fe9cddf5cab0b369 1707 chrony_1.26-2.dsc
c13adbba2a6c263784daec988a50a5cafa508928 17977 chrony_1.26-2.diff.gz
21b32ab2bc52fada70b151fc74ef5b047dea32a7 392806 chrony_1.26-2_amd64.deb
Checksums-Sha256:
ce05219edb4b3c47831a1b99c37fe75db4166ac97608ba0bfd7efec59defb3a2 1707
chrony_1.26-2.dsc
c3c5977aec0372207d5840786f674eca428b73fde319baf893ca7d57ab03c9d3 17977
chrony_1.26-2.diff.gz
b00dab5f9b9647dc265455fee5fc9b55a43d6d0da4a3ee3aba5e5948c8dcf69a 392806
chrony_1.26-2_amd64.deb
Files:
d655f75bbc9e80ec51bedc0ad963666d 1707 admin extra chrony_1.26-2.dsc
b62ae11179aa5dd0e4d6c725b785d45c 17977 admin extra chrony_1.26-2.diff.gz
9e86a58095ffc45ae4a747ddac36f3a6 392806 admin extra chrony_1.26-2_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBCAAGBQJP8gyIAAoJEHNAHjW0+9qlXXUQAI5dFz0ykaGj3Ql1lndcPrit
XIrmqtK8oi+GIUJi7ubRh/Q7IPuDeuOX7oaZzXWxBQLWmKm4I9AMYAkK88UfjcpT
qkxrSdrvtuQ6zA+9j4zml1FBwFNJHvgfRhahwoSeHowyoSmKHS+CBC05hzL0C6yu
gr8s/8cp3DERZp5KLKruX9Kj8+Ybi6fkpqltI4lfa12mQOnicy680eiVYLN8C596
gwmXla1+1u9UT4UrcX//4aNb16y6kytp4l4Pb67ruwBYUEe+Xl1P0tZzmJCUixjo
CrKTTfeAyVLMH0G3f/Enco57CEm/21p56si+PUxo2K1y/HXlEv286Xmhnpl5hewz
U4DatFg3N4Gx859Fxjn87LwKWt2VVD7tQiER7+kg/0uwwAbvM3w+7t7qW/B0UFB2
mRPSORQWqDIi4j8A2BmncYNJclatruCLEkqnAFF8giGxPOxBEY0+8CKWuPmFq5Vi
a+LKbMDW/ZGtk4ljNGg/zZaWqSAJikNvfLfg84vYg04TvmABM/X66TwHM53cetfb
bEQPjbrnGywIKDvjVeGIMn+eiGnLc2bNojGOwP8bsPb5iNoDFc6J4uib3A1qM7Qr
zFvIhfcu11g+MIlAQSjYc/WM/3nJKK/vOEZS9QKj1tQwg8py0oMF+9O/0AC53ZFO
8U/HgXzQ/+rGiBAlDA9y
=r9x+
-----END PGP SIGNATURE-----
--- End Message ---
