Your message dated Sat, 8 Sep 2018 00:05:51 +0200 with message-id <[email protected]> and subject line Closing old bugs has caused the Debian Bug report #612451, regarding possible bug in ntp package 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.) -- 612451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612451 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ntp Version: 1:4.2.6.p2+dfsg-1+b1 Severity: normal *** Please type your report below this line *** Hello, I found that ntp may not startup / run correct in Debian 6. Using ntpq the local clock is shown as not used. ntpq> pe remote refid st t when poll reach delay offset jitter ============================================================================== alix01 192.168.1.50 3 u 278 1024 377 0.390 3.523 6.058 *zaphod 192.53.103.108 2 u 114 1024 377 9.920 1.948 3.027 LOCAL(0) .LOCL. 8 l 46h 64 0 0.000 0.000 0.000 ntpq> q I read the changelog and found that ntp may be started by ifup so I thought it may be caused because the loopback address may not be set up at this moment. So I restarted ntp and now it looks like this: ntpq> pe remote refid st t when poll reach delay offset jitter ============================================================================== alix01 192.168.1.50 3 u 5 64 3 0.367 3.951 0.053 zaphod 192.53.103.108 2 u 2 64 3 1.698 5.980 0.149 *LOCAL(0) .LOCL. 8 l 4 64 3 0.000 0.000 0.000 ntpq> q But then ... after a while ... I looked again. ntpq> pe remote refid st t when poll reach delay offset jitter ============================================================================== alix01 192.168.1.50 3 u 2 128 377 0.357 -0.617 1.658 *zaphod 192.53.103.108 2 u 117 128 377 1.678 3.576 2.166 LOCAL(0) .LOCL. 8 l 229m 64 0 0.000 0.000 0.000 ntpq> q The local clock seems to be gone as soon ntp switches zu a real time server ... or such like. I verified this on another Deb 6 system. For me this looks like a real bug. Best regards, Stephan -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (900, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages ntp depends on: ii adduser 3.112+nmu2 add and remove users and groups ii dpkg 1.15.8.10 Debian package management system ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libcap2 1:2.19-3 support for getting/setting POSIX. ii libedit2 2.11-20080614-2 BSD editline and history libraries ii libopts25 1:5.10-1.1 automated option processing librar ii libssl0.9.8 0.9.8o-4 SSL shared libraries ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii netbase 4.45 Basic TCP/IP networking system Versions of packages ntp recommends: ii perl 5.10.1-17 Larry Wall's Practical Extraction Versions of packages ntp suggests: pn ntp-doc <none> (no description available) -- Configuration Files: /etc/ntp.conf changed: driftfile /var/lib/ntp/ntp.drift statsdir /var/log/ntpstats/ statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day enable server 192.168.1.9 server 192.168.1.50 server 127.127.1.0 fudge 127.127.1.0 stratum 8 restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery restrict 127.0.0.1 restrict ::1 -- no debconf information
--- End Message ---
--- Begin Message ---Hello, thank you for spending your time helping to make Debian better with this bug report. Unfortunately your bug report could not be (completely) dealt with in an appropriate time. The version you have filed this bug report against is for a release that is not supported anymore. Unfortunately we do not have the manpower to reproduce bugs that old. It is possibly already fixed with the current version. Therefor I'm closing this bug. If you can still reproduce this issue on a supported release (Debian 9 aka stretch, preferably also in sid) feel free to reopen the bug report. Thanks, Bernhard
--- End Message ---
