[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1008059: marked as done (systemd-timesyncd restarted on every router advertisment)

Your message dated Wed, 29 Jun 2022 18:10:12 +0000
with message-id <E1o6c8i-000BBY-PA@fasolo.debian.org>
and subject line Bug#1008059: fixed in dhcpcd5 9.4.1-2
has caused the Debian Bug report #1008059,
regarding systemd-timesyncd restarted on every router advertisment
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 owner@bugs.debian.org
immediately.)


-- 
1008059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008059
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: systemd-timesyncd
Version: 250.4-1
Severity: normal
Tags: ipv6

Dear Maintainer,

I'm seeing systemd restart systemd-timesyncd.service approximately every
10 seconds, lining up with when I see a log showing that my router has
advertised its IPv6 address.

If I run `journalctl -f`, the output is full of lines like the
following:

```
Mar 21 15:53:56 lucy.dinwoodie.org dhcpcd[452]: eth0: Router Advertisement from fe80::be99:11ff:fe69:4300
Mar 21 15:53:57 lucy.dinwoodie.org systemd[1]: Stopping Network Time Synchronization...
Mar 21 15:53:57 lucy.dinwoodie.org systemd[1]: systemd-timesyncd.service: Deactivated successfully.
Mar 21 15:53:57 lucy.dinwoodie.org systemd[1]: Stopped Network Time Synchronization.
Mar 21 15:53:57 lucy.dinwoodie.org systemd[1]: Starting Network Time Synchronization...
Mar 21 15:53:57 lucy.dinwoodie.org systemd[1]: Started Network Time Synchronization.
Mar 21 15:53:57 lucy.dinwoodie.org systemd-timesyncd[6426]: Initial synchronization to time server 162.159.200.1:123 (0.debian.pool.ntp.org).
Mar 21 15:54:06 lucy.dinwoodie.org dhcpcd[452]: eth0: Router Advertisement from fe80::be99:11ff:fe69:4300
Mar 21 15:54:07 lucy.dinwoodie.org systemd[1]: Stopping Network Time Synchronization...
Mar 21 15:54:07 lucy.dinwoodie.org systemd[1]: systemd-timesyncd.service: Deactivated successfully.
Mar 21 15:54:07 lucy.dinwoodie.org systemd[1]: Stopped Network Time Synchronization.
Mar 21 15:54:07 lucy.dinwoodie.org systemd[1]: Starting Network Time Synchronization...
Mar 21 15:54:07 lucy.dinwoodie.org systemd[1]: Started Network Time Synchronization.
Mar 21 15:54:07 lucy.dinwoodie.org systemd-timesyncd[6463]: Initial synchronization to time server 178.62.18.76:123 (0.debian.pool.ntp.org).
```

There's no great immediate impact, but it seems like this shouldn't be
happening.  And there is clearly some impact in terms of unnecessary
disk churn, unnecessary network usage, unnecessary load on NTP servers,
and -- still minor, but most relevant to my immediate interests --
ability to spot interesting logs in journald.

Some searching online led me to a very old systemd bug[0], but that was
apparently resolved in systemd 219, so definitely shouldn't be relevant
now.

[0]: https://bugs.freedesktop.org/show_bug.cgi?id=87505

Other searches pointed me to other people reporting similar
problems[1][2] with no resolution. It's possibly of interest is that
they're all folk (like me) running on a Raspberry Pi.  At least in my
case, however, I understand the only difference between what I'm running
and a regular arm64 Debian installation is that there are a few driver
and firmware packages shipped from the Raspberry Pi Foundation.
Certainly all the systemd packages I'm using have come straight from
deb.debian.org repositories.

[1]: https://raspberrypi.stackexchange.com/q/133605/145463
[2]: https://forums.raspberrypi.com/viewtopic.php?t=324473

Given that, I suspect whatever the issue is may be due to one or more of
(a) folks using Raspberry Pis are going to be running an arm-based
architecture, or (b) folks using Pis are more likely to be running very
minimal Debian installations, so are more likely to have not installed
packages that might not be listed as dependencies but whose absence
causes non-obvious problems.

Admittedly there's also (c) there's something up with the config that's
used on Raspberry Pis by default, but I've done my best to rule that
out: I can't see anything in the documentation for dhcpcd,
systemd-networkd or systemd-timesyncd that would cause this behaviour,
nor anything in any of the configuration in /etc/systemd/.

I'm seeing this behaviour on /bullseye (247.3-6), /bullseye-backports
(250.4-1~bpoll+1), and /sid (250.4-1).

-- System Information:
Debian Release: 11.2
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'stable'), (850, 'testing'), (500, 'unstable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.10.103-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-timesyncd depends on:
ii  adduser  3.118
ii  libc6    2.33-7
ii  systemd  250.4-1

systemd-timesyncd recommends no packages.

systemd-timesyncd suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Source: dhcpcd5
Source-Version: 9.4.1-2
Done: Martin-Éric Racine <martin-eric.racine@iki.fi>

We believe that the bug you reported is fixed in the latest version of
dhcpcd5, which is due to be installed in the Debian FTP archive.

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 1008059@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin-Éric Racine <martin-eric.racine@iki.fi> (supplier of updated dhcpcd5 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 27 Jun 2022 22:37:37 +0300
Source: dhcpcd5
Binary: dhcpcd-base dhcpcd-base-dbgsym dhcpcd5
Architecture: source amd64 all
Version: 9.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Martin-Éric Racine <martin-eric.racine@iki.fi>
Changed-By: Martin-Éric Racine <martin-eric.racine@iki.fi>
Description:
 dhcpcd-base - DHCPv4 and DHCPv6 dual-stack client (binaries and exit hooks)
 dhcpcd5    - DHCPv4 and DHCPv6 dual-stack client (init.d script and systemd un
Closes: 980861 1001763 1008059 1013430 1013763
Changes:
 dhcpcd5 (9.4.1-2) unstable; urgency=medium
 .
   [ Martin-Éric Racine ]
   * Adopt package (Closes: #1013763).
     Thanks to Scott Leggett for having maintained the package in recent years.
   * Implement privilege separation (Closes: #1013430).
     + Add to [rules]:
       --privsepuser=dhcpcd
     + Add to [posinst]: dhcpcd system user creation.
     + Add to [postrm]: dhcpcd system user deletion.
     + Add to [control]: Depends: adduser
   * Bump Standards-Version to 4.6.1 (no change required).
   * Merge patch against hooks/60-ntp-common.conf (Closes: #1008059).
   * Move path of Chrony helper from /usr/lib to /usr/libexec (Closes: #980861).
   * Fix openntpd restart command (Closes: #1001763).
   * Split package into two targets:
     + dhcpcd-base (binaries, exit hooks and manual pages) Provides: dhcp-client
     + dhcpcd5 (init.d script and systemd unit) Depends: dhcpcd-base
     Thus dhcpcd-base provides a dhcp-client backend for ifupdown that offers
     a dual-stack replacement for isc-dhcp-client.
     Meanwhile dhcpcd5 still exists for minimalist systems without ifupdown.
   [ Scott Leggett ]
   * Avoid pointless NTP client reloads
   * Add local gbp.conf for upstream tag format.
   * Add to [control]:
     + Rules-Requires-Root: no
   * Tests: work around issue with checksums on veth interfaces.
   * Tests: Give NTP services more grace time for updates.
   * Add support for systemd unit file hardening.
   [ Bastian Germann ]
   * Update rundir to align with upstream.
   [ Julien Rabier ]
   * Update the systemd unit.
   * Add a systemd unit template for interface-specific cases.
Checksums-Sha1:
 09237debeaa9bb48e7436ebc661906e3d1421b5a 1854 dhcpcd5_9.4.1-2.dsc
 bf8fa944cf04843c494ed8df718dcbf6dc3274d2 14632 dhcpcd5_9.4.1-2.debian.tar.xz
 deeaff6c07a6e16b940af3694ab12aa74c8030dd 455424 dhcpcd-base-dbgsym_9.4.1-2_amd64.deb
 4c23d5b048dc8becce500441085ec02f6effc3c2 189716 dhcpcd-base_9.4.1-2_amd64.deb
 95979fabefced3e4ceb06196664d9b1a3810b414 9800 dhcpcd5_9.4.1-2_all.deb
 7c2d025c47f03da21beb37e74b43650ba9f79643 6121 dhcpcd5_9.4.1-2_amd64.buildinfo
Checksums-Sha256:
 cd220742061a3aeb8730a8579255019061103ddda9cb4a715a7dd1911f531123 1854 dhcpcd5_9.4.1-2.dsc
 47cc3b7975b1004ed8c0e69fd8e6e7ca22c43411684dee84e1737c0634718029 14632 dhcpcd5_9.4.1-2.debian.tar.xz
 b4fd1bdd9a68997ac06d0240ee6d396d72e447500d793679c7cb57e0f066f710 455424 dhcpcd-base-dbgsym_9.4.1-2_amd64.deb
 ff7915b2954233304e154e7d8224c3aa95114c4978a444b6ac88be5ff6046819 189716 dhcpcd-base_9.4.1-2_amd64.deb
 01d95de0083f34ce6ee5462e6508d7db91d73db078cb129cde7dee3ef69acfe7 9800 dhcpcd5_9.4.1-2_all.deb
 27b817a7e78bef64b7c89f374de23d14531c0fbe35ceb50da3274f94a574ffea 6121 dhcpcd5_9.4.1-2_amd64.buildinfo
Files:
 f075b70f7b1090d20650a88c0edade98 1854 net optional dhcpcd5_9.4.1-2.dsc
 beb14820fe1d36f4ce403f7f69a16695 14632 net optional dhcpcd5_9.4.1-2.debian.tar.xz
 883d37b87d72ce0190759d1ac029558d 455424 debug optional dhcpcd-base-dbgsym_9.4.1-2_amd64.deb
 84875820dacaf807188acec279ffa972 189716 net optional dhcpcd-base_9.4.1-2_amd64.deb
 0145003401454502dcfc0bd598e33ff9 9800 net optional dhcpcd5_9.4.1-2_all.deb
 49220ae5a6a821aabacfdcdfd66597d4 6121 net optional dhcpcd5_9.4.1-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmK7g8AQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFIanC/935JsoNONQdBCf/Obw4KBfmW1x5DoSQnsv
ciFuFdGyycowNb6rdkF3Xg4LBf21rh0CzaImzTQ+CF9VD/hn+XuLmFCHHf5muXW0
akk4An27HcvrqhqjuoP/uHAxRAdIzLDkdruRlf9I8/U/fTyGcEX65/Gwbq73Hq56
kwywrFKwVi1+bunJNl3PyzAV8hrmYhNCfIp7O1DNoon2LJgt16LG3GSyePPcSW+g
PIVkd44EW8/61mVEVwFXnukRs1hK58/UHXnwFZL1CMtbFIS6a9thsrn7Zv5H182t
66ASXz20AuxRmu+XKg57AtbcnhUB+m320A6W34L1RzehT1ZzJTbRWVmem9PNHcPo
0B64nmg6sQOgaPhjl3ZoNt2r+49in14PhbJp5c4TAbyPUWqwWLCtESqQ5pNBo4M4
OeDOYNLPx5hQQVL8u/zR7cbVUJjf4nWT3pJ0pWNhGBqkK+C/H3R7qSJyXV7rsXMe
lpde06+6wkBnYJpAXCIcf9V4bSGYD4o=
=FLTv
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: