Your message dated Mon, 16 Nov 2015 22:57:24 +0100
with message-id <[email protected]>
and subject line Bug#254421: chrony: Chrony floods the network with ntp requests
has caused the Debian Bug report #254421,
regarding chrony: Chrony floods the network with ntp requests
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.)
--
254421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=254421
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 1.20-5
Severity: important
Tags: patch
Chrony goes crazy if the system time is ahead of the actual time after
correcting the clock. This is because a backwards jump in the clock
disturbs the timing mechanism in chrony, making it think that all ntp
requests timeout immediately.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8
Versions of packages chrony depends on:
ii libc6 2.3.2.ds1-12 GNU C Library: Shared libraries an
ii libncurses5 5.4-3 Shared libraries for terminal hand
ii libreadline4 4.3-10 GNU readline and history libraries
-- no debconf information
431c431,433
<
---
>
> struct timeval compare;
>
450a453,465
>
> /* Check for a backward clock jump
> * and avoid constant looping by returning and getting
> * a new value for *now */
>
> LCL_ReadRawTime(&compare);
>
> if (UTI_CompareTimevals(now, &compare) >= 0){
> LOG(LOGS_INFO, LOGF_Scheduler, "Backward jump in clock, exiting dispatch_timeouts()");
> break;
> }
>
>
--- End Message ---
--- Begin Message ---
Hello,
As there have been no answers since 2008, I’m closing this bug report.
Feel free to reopen it if you still can reproduce the issue.
Thanks,
Vincent
--- End Message ---
