Your message dated Sun, 27 Apr 2008 02:17:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#447011: fixed in chrony 1.23-3
has caused the Debian Bug report #447011,
regarding chronyd stalls with 100% CPU usage
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.)


-- 
447011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447011
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: chrony
Version: 1.21z-5
Severity: normal


Hi,

Sometimes chronyd starts using 100% CPU time. This happens 1-5 seconds
after the /etc/ppp/ip-up.d/chrony script marked the sources online. In
this state chronyd does not accept any new chronyc commands (chronyc
just hangs indefinitely). In fact, using strace shows that chronyd is not
performing any system calls, so it is spinning in some internal
function.

The problem is not 100% reproducible but it seems to happen more
frequently with some time sources than with others. For example,  having
84.2.40.31 (ntp.t-online.hu) in chrony.conf show this problem rather
frequently now but AFAIR last week it mostly worked OK.

Stopping/restarting chronyd sometimes fixes the problem, sometimes it
starts spinning again.

I also observed the bug on servers running etch, but not frequently
(they were configured to use pool.ntp.org so it may depend on what
servers did they happen to use).

There is nothing interesting in syslog; a couple of times I tried
running "chronyd -d" but then I could never reproduce the bug - so the
bug may also be in the logging code and not related to the time
sources...

Gabor

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22.6
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages chrony depends on:
ii  libc6                     2.6.1-5        GNU C Library: Shared libraries
ii  libncurses5               5.6+20071006-1 Shared libraries for terminal hand
ii  libreadline5              5.2-3          GNU readline and history libraries
ii  ucf                       3.003          Update Configuration File: preserv

chrony recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Source: chrony
Source-Version: 1.23-3

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.23-3.diff.gz
  to pool/main/c/chrony/chrony_1.23-3.diff.gz
chrony_1.23-3.dsc
  to pool/main/c/chrony/chrony_1.23-3.dsc
chrony_1.23-3_i386.deb
  to pool/main/c/chrony/chrony_1.23-3_i386.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 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: SHA1

Format: 1.7
Date: Sat, 26 Apr 2008 11:47:44 -0500
Source: chrony
Binary: chrony
Architecture: source i386
Version: 1.23-3
Distribution: unstable
Urgency: high
Maintainer: John Hasler <[EMAIL PROTECTED]>
Changed-By: John Hasler <[EMAIL PROTECTED]>
Description: 
 chrony     - Sets your computer's clock from time servers on the Net
Closes: 434483 447011 474294
Changes: 
 chrony (1.23-3) unstable; urgency=high
 .
   * Rewrote UTI_NormaliseTimeval()in util.c to use divide/remainder
     instead of loops at the suggestion of Gabor Gombas.  This prevents the
     problem of the loop running until the sun goes out when the function
     is called with a very large value for tv_usec on 64-bit architectures.
     Also fixed some other spots where the same loop was being used.
 .
     Closes: #474294 Goes into endless loop
     Closes: #447011 chronyd stalls with 100% CPU usage
 .
     I still don't know why the function is being called with such a
     large value, however.
 .
   * Changed default servers in chrony,conf to Debian servers.
 .
     Closes: #434483: chrony: Should use NTP servers in Debian pool
Files: 
 6d8544cc90542d2cac6ee47e79e1c3e7 723 admin extra chrony_1.23-3.dsc
 3553b826eed0cd269f077ccbffd40fbc 156904 admin extra chrony_1.23-3.diff.gz
 c961455b8706e32969dc4a60d384ed63 324114 admin extra chrony_1.23-3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQCVAwUBSBPCVPc1CeQKxb5hAQL66AP8CyfgJ4HZmI3JmKzw2yMBA9V4j8k0tu/e
4VnSjw76TP1JYWR/eUMtAixgLpjiRE4hYvqTU4VHbsLwqMJryHgD2QQNrH+ej6yg
Z+wLZ9Q1Y4jTLgVTQIFOnO5dKy3NVwmDpGJq4kGacFBS6yW4GWwdctGwUH7Ys9hL
/F9QgEZGTlY=
=0Wtx
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to