Your message dated Sat, 29 Aug 2020 16:45:49 +0200
with message-id <[email protected]>
and subject line Re: systemd-timesyncd: time synchronization suddenly stopped 
working
has caused the Debian Bug report #964444,
regarding systemd-timesyncd: poll interval should not be increased during 
network failures
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.)


-- 
964444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964444
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd-timesyncd
Version: 245.6-1
Severity: important

systemd-timesyncd no longer seems to work. I couldn't find any reason in the 
logs.
Now there's a 5-second delta!

zira:~> timedatectl timesync-status
       Server: (null) (3.debian.pool.ntp.org)   
Poll interval: 34min 8s (min: 32s; max 34min 8s)
         Leap: normal                           
      Version: 4                                
      Stratum: 2                                
    Reference: 596DFB17                         
    Precision: 1us (-24)                        
Root distance: 40.580ms (max: 5s)               
       Offset: -1.087495s                       
        Delay: 2.156880s                        
       Jitter: 2.300948s                        
 Packet count: 620                              

zira:~> timedatectl show-timesync
FallbackNTPServers=0.debian.pool.ntp.org 1.debian.pool.ntp.org 
2.debian.pool.ntp.org 3.debian.pool.ntp.org
ServerName=3.debian.pool.ntp.org
RootDistanceMaxUSec=5s
PollIntervalMinUSec=32s
PollIntervalMaxUSec=34min 8s
PollIntervalUSec=34min 8s
NTPMessage={ Leap=0, Version=4, Mode=4, Stratum=2, Precision=-24, 
RootDelay=30.776ms, RootDispersion=25.192ms, Reference=596DFB17, 
OriginateTimestamp=Mon 2020-07-06 20:06:14 CEST, ReceiveTimestamp=Mon 
2020-07-06 20:06:14 CEST, TransmitTimestamp=Mon 2020-07-06 20:06:14 CEST, 
DestinationTimestamp=Mon 2020-07-06 20:06:16 CEST, Ignored=yes PacketCount=620, 
Jitter=2.300948s }
Frequency=32768000

zira:~> systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
     Active: active (running) since Sat 2020-07-04 00:39:52 CEST; 3 days ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 684 (systemd-timesyn)
     Status: "Idle."
      Tasks: 2 (limit: 19071)
     Memory: 2.8M
     CGroup: /system.slice/systemd-timesyncd.service
             └─684 /lib/systemd/systemd-timesyncd

Jul 05 23:40:38 zira systemd-timesyncd[684]: Timed out waiting for reply from 
37.187.174.185:123 (1.debian.pool.ntp.org).
Jul 05 23:40:51 zira systemd-timesyncd[684]: Initial synchronization to time 
server 185.51.192.34:123 (2.debian.pool.ntp.org).
Jul 06 10:50:50 zira systemd-timesyncd[684]: Initial synchronization to time 
server 51.15.191.239:123 (0.debian.pool.ntp.org).
Jul 06 12:30:47 zira systemd-timesyncd[684]: Initial synchronization to time 
server 4.53.160.75:123 (0.debian.pool.ntp.org).
Jul 06 13:50:59 zira systemd-timesyncd[684]: Initial synchronization to time 
server 91.206.16.3:123 (0.debian.pool.ntp.org).
Jul 06 14:08:11 zira systemd-timesyncd[684]: Initial synchronization to time 
server 162.159.200.1:123 (0.debian.pool.ntp.org).
Jul 06 17:32:15 zira systemd-timesyncd[684]: Initial synchronization to time 
server 193.70.90.148:123 (0.debian.pool.ntp.org).
Jul 06 19:53:13 zira systemd-timesyncd[684]: Initial synchronization to time 
server 94.130.184.193:123 (0.debian.pool.ntp.org).
Jul 06 19:57:43 zira systemd-timesyncd[684]: Timed out waiting for reply from 
94.130.184.193:123 (0.debian.pool.ntp.org).
Jul 06 19:57:44 zira systemd-timesyncd[684]: Initial synchronization to time 
server 91.207.136.55:123 (0.debian.pool.ntp.org).

If I understand the "timedatectl show-timesync" output, it stopped
working on 2020-07-06 20:06:16 CEST. I suspended my laptop shortly
after this time. But I do that several times a day. The only awkward
thing I could notice in the logs is thousands of messages

Jul 07 01:36:34 zira systemd-logind[837]: Got message type=signal sender=:1.0 
destination=n/a path=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=Reloading cookie=9958 
reply_cookie=0 signature=b error-name=n/a error-message=n/a
Jul 07 01:36:34 zira systemd-logind[837]: Got message type=signal sender=:1.0 
destination=n/a path=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=UnitRemoved cookie=9959 
reply_cookie=0 signature=so error-name=n/a error-message=n/a
Jul 07 01:36:34 zira systemd-logind[837]: Got message type=signal sender=:1.0 
destination=n/a path=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=UnitRemoved cookie=9960 
reply_cookie=0 signature=so error-name=n/a error-message=n/a
Jul 07 01:36:34 zira systemd-logind[837]: Got message type=signal sender=:1.0 
destination=n/a path=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=UnitRemoved cookie=9961 
reply_cookie=0 signature=so error-name=n/a error-message=n/a
Jul 07 01:36:34 zira systemd-logind[837]: Got message type=signal sender=:1.0 
destination=n/a path=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=UnitRemoved cookie=9962 
reply_cookie=0 signature=so error-name=n/a error-message=n/a
Jul 07 01:36:34 zira systemd-logind[837]: Got message type=signal sender=:1.0 
destination=n/a path=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=UnitRemoved cookie=9963 
reply_cookie=0 signature=so error-name=n/a error-message=n/a
Jul 07 01:36:34 zira systemd-logind[837]: Got message type=signal sender=:1.0 
destination=n/a path=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=UnitRemoved cookie=9964 
reply_cookie=0 signature=so error-name=n/a error-message=n/a
[...]

some time later.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd-timesyncd depends on:
ii  adduser  3.118
ii  libc6    2.30-8
ii  systemd  245.6-1

systemd-timesyncd recommends no packages.

systemd-timesyncd suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

--- End Message ---
--- Begin Message ---
Version: 246-1

Thanks for forwarding this upstream.
I see that this has been addressed in
https://github.com/systemd/systemd/pull/16624 which is part of v246, so
closing the bug report accordingly.



Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to