Your message dated Sun, 10 Sep 2017 16:17:46 +0200
with message-id <[email protected]>
and subject line Re: Troublesome systemd-networkd-wait-online.service
has caused the Debian Bug report #875303,
regarding Troublesome systemd-networkd-wait-online.service
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.)
--
875303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875303
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 234-3
Severity: normal
The systemd-networkd-wait-online.service is causing tlp.service (among
others) to break in my setup.
The issue is caused by the rule
Also=systemd-networkd-wait-online.service
present in systemd-network.service. Several services include include an
explicit dependency on network-online.target which then drag in
systemd-networkd-wait-online.service. One is apt-daily.service, but
exim4 (via LFS) is another.
The net result is that multi-user.target now depends on
systemd-networkd-wait-online.service. However, on a laptop, this is
broken. multi-user.target shouldn't directly depend on a working
connection.
In case of tlp.service, which has After=multi-user.target, will execute
the startup rules *after* wait-online timeouts, which is some minutes
after I could login.
Incidentally, exim4 also isn't started until timeout occurs, which makes
local mail delivery broken until then.
This is more subtle. The init script in this case depends on $network.
systemd shouldn't automatically translate this to include
network-online.target, but only network.target.
I currently masked network-online.service to resolve this issue, but
this shouldn't be. Services should be able to depend on network-online
without affecting system startup.
-- Package-specific info:
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.116
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.11.0-10
ii libaudit1 1:2.7.7-1+b2
ii libblkid1 2.29.2-4
ii libc6 2.24-17
ii libcap2 1:2.25-1
ii libcryptsetup4 2:1.7.3-4
ii libgcrypt20 1.8.1-1
ii libgpg-error0 1.27-3
ii libidn11 1.33-1
ii libip4tc0 1.6.1-2
ii libkmod2 24-1
ii liblz4-1 0.0~r131-2+b1
ii liblzma5 5.2.2-1.3
ii libmount1 2.29.2-4
ii libpam0g 1.1.8-3.6
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.7-1
ii libsystemd0 234-3
ii mount 2.29.2-4
ii procps 2:3.3.12-3
ii util-linux 2.29.2-4
Versions of packages systemd recommends:
ii dbus 1.11.16+really1.11.16-2
ii libpam-systemd 234-3
Versions of packages systemd suggests:
ii policykit-1 0.105-18
pn systemd-container <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.130
ii udev 234-3
-- Configuration Files:
/etc/systemd/journald.conf changed [not included]
/etc/systemd/logind.conf changed [not included]
/etc/systemd/resolved.conf changed [not included]
/etc/systemd/timesyncd.conf changed [not included]
--- End Message ---
--- Begin Message ---
On Sun, 10 Sep 2017 15:57:17 +0200 Yuri D'Elia <[email protected]> wrote:
> Package: systemd
> Version: 234-3
> Severity: normal
>
> The systemd-networkd-wait-online.service is causing tlp.service (among
> others) to break in my setup.
>
> The issue is caused by the rule
>
> Also=systemd-networkd-wait-online.service
>
> present in systemd-network.service. Several services include include an
> explicit dependency on network-online.target which then drag in
> systemd-networkd-wait-online.service. One is apt-daily.service, but
> exim4 (via LFS) is another.
>
> The net result is that multi-user.target now depends on
> systemd-networkd-wait-online.service. However, on a laptop, this is
> broken. multi-user.target shouldn't directly depend on a working
> connection.
>
> In case of tlp.service, which has After=multi-user.target, will execute
> the startup rules *after* wait-online timeouts, which is some minutes
> after I could login.
>
> Incidentally, exim4 also isn't started until timeout occurs, which makes
> local mail delivery broken until then.
>
> This is more subtle. The init script in this case depends on $network.
> systemd shouldn't automatically translate this to include
> network-online.target, but only network.target.
>
> I currently masked network-online.service to resolve this issue, but
> this shouldn't be. Services should be able to depend on network-online
> without affecting system startup.
If you have systemd-networkd-wait-online.servce enabled and a service
has Wants/After=network-online.target it's totally correct that
systemd-network-wait-online.service is pulled in and ordered accordingly.
That's not a bug but intended behaviour, so closing.
Fwiw, systemd-network.service does not have
Also=systemd-network-wait-online.service.
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/units/systemd-networkd.service.m4.in
Not quite sure which file you are looking at there.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
