Your message dated Thu, 19 Oct 2023 16:08:18 +0200
with message-id <[email protected]>
and subject line Re: Bug#1054211: systemd: ystemd-networkd-wait-online.service
reports a timeout error while network is activated
has caused the Debian Bug report #1054211,
regarding systemd: ystemd-networkd-wait-online.service reports a timeout error
while network is activated
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.)
--
1054211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054211
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 254.5-1
Severity: normal
I think this is related to the new version of package network manager
systemd-analyze blame
2min 117ms systemd-networkd-wait-online.service
7.850s NetworkManager-wait-online.service
1.219s NetworkManager.service
1.038s udisks2.service
1.007s privoxy.service
938ms ModemManager.service
807ms systemd-binfmt.service
805ms systemd-networkd.service
728ms systemd-timesyncd.service
629ms cpufrequtils.service
603ms systemd-modules-load.service
510ms [email protected]
384ms upower.service
323ms dev-nvme0n1p5.device
235ms accounts-daemon.service
225ms systemd-udev-trigger.service
217ms run-rpc_pipefs.mount
212ms cups.service
207ms smbd.service
191ms exim4.service
189ms [email protected]
139ms binfmt-support.service
130ms loadcpufreq.service
124ms networking.service
119ms nmbd.service
109ms avahi-daemon.service
108ms apparmor.service
108ms polkit.service
107ms [email protected]
105ms systemd-journal-flush.service
102ms dbus.service
100ms e2scrub_reap.service
98ms proc-sys-fs-binfmt_misc.mount
79ms systemd-logind.service
79ms [email protected]
74ms boot-efi.mount
-- Package-specific info:
-- System Information:
Debian Release: trixie/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-13-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii libacl1 2.3.1-3
ii libaudit1 1:3.1.1-1
ii libblkid1 2.39.2-4
ii libc6 2.38-3
ii libcap2 1:2.66-4
ii libcryptsetup12 2:2.6.1-5
ii libfdisk1 2.39.2-4
ii libgcrypt20 1.10.2-3
ii libkmod2 30+20230601-2
ii liblz4-1 1.9.4-1
ii liblzma5 5.4.4-0.1
ii libmount1 2.39.2-4
ii libp11-kit0 0.25.0-5
ii libseccomp2 2.5.4-1+b3
ii libselinux1 3.5-1
ii libssl3 3.1.3-1
ii libsystemd-shared 254.5-1
ii libsystemd0 254.5-1
ii libzstd1 1.5.5+dfsg2-2
ii mount 2.39.2-4
ii systemd-dev 254.5-1
Versions of packages systemd recommends:
ii dbus [default-dbus-system-bus] 1.15.8-2
ii systemd-timesyncd [time-daemon] 254.5-1
Versions of packages systemd suggests:
ii libfido2-1 1.13.0-1+b1
ii libqrencode4 4.1.1-1
ii libtss2-esys-3.0.2-0 4.0.1-3
ii libtss2-mu0 4.0.1-3
ii libtss2-rc0 4.0.1-3
ii polkitd 123-1
ii python3 3.11.4-5+b1
pn python3-pefile <none>
pn systemd-boot <none>
pn systemd-container <none>
pn systemd-homed <none>
pn systemd-resolved <none>
pn systemd-userdbd <none>
Versions of packages systemd is related to:
ii dbus-user-session 1.15.8-2
pn dracut <none>
ii initramfs-tools 0.142
ii libnss-systemd 254.5-1
ii libpam-systemd 254.5-1
ii udev 254.5-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 19.10.23 um 15:28 schrieb Eric Valette:
On 19/10/2023 15:23, Michael Biebl wrote:
On 10/19/23 10:47, eric wrote:
Package: systemd
Version: 254.5-1
Severity: normal
Do you have any network interfaces managed by systemd-networkd?
If not, why is systemd-networkd-wait-online.service enabled?
How do I specify/know that? I havent changed my network config besides
regular package update.
I would assume if you configured networkd to manage your network, you
would know that.
Apparently you haven't, so let's assume you don't use networkd.
I've no /etc/network/interface file and my config should be managed by
network manager. Currently ethernet cable but wifi sometimes.
/etc/network/interfaces is for ifupdown, unrelated to networkd.
In any case: It seems you are not using networkd, then you shouldn't use
systemd-networkd-wait-online.service either.
Apparently it is enabled for you: disable it via
systemctl disable systemd-networkd-wait-online.service
Closing
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
