Your message dated Wed, 24 Nov 2021 17:38:42 +0100
with message-id <[email protected]>
and subject line Re: Bug#1000510: systemd: all server programs fail when they
are set to specified interfaces
has caused the Debian Bug report #1000510,
regarding systemd: all server programs fail when they are set to specified
interfaces
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.)
--
1000510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000510
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 247.3-6
Severity: important
systemd-networkd causes issues around services that do not have
"network-online.target" as part of "Wanted=" in their unit file.
For example,
apache2.service has the following under their [Unit] in apache2.service,
"After=network.target remote-fs.target nss-lookup.target"
, this is invalid, as it should rather be::
"After=network.target network-online.target remote-fs.target
nss-lookup.target"
same goes for ssh.service
"After=network.target auditd.service",
should be
"After=network.target network-online.target auditd.service"
and for any other service omitting network-online.target..
. otherwise those services will say "fail" on boot-up.. without any
other further detail.
journactl -xe -u doesn't show any further detail other that the service
failed to "bind" to an address.
^ The ssh service I have set is set to bind to a "specific" interface
that is defined by systemd-networkd's settings in /etc/systemd/network.
(networkctl was shows fully configured interfaces, so there is no issue
happening over here)
The apache2 service is also set to bind to a "specific" interface.
^ By default these services run on 0.0.0.0 -- to run on all interfacaes,
including 127.0.0.1 << which is pretty much ready much earlier. This
explains as to why there is failure when the user defines specified
interfaces later on.
.. whoever is in charge of systemd, should inform other server-package
maintainers to add "network-online.target" as a dependency-check
otherwise those services will fail to start when the user decides to use
specific interfaces.
thanks
--- End Message ---
--- Begin Message ---
This is not an issue that can be solved in the systemd package, thus
closing.
It's up to the individual packages to decide, whether they want to order
themselves after network-online.target or not or if they use other
mechanisms.
In your particular case, since you use a non-default configuration of
binding to a specific port, it could even be argued that it is your
responsibility to adjust the service file accordingly. Thankfully this
is trivially easy to do via a drop-in snippet, like this.
$ cat /etc/systemd/system/apache2.service.d/override.conf
[Unit]
Wants=network-online.target
After=network-online.target
Regards,
Michael
On 24.11.21 13:19, westlake wrote:
Package: systemd
Version: 247.3-6
Severity: important
systemd-networkd causes issues around services that do not have
"network-online.target" as part of "Wanted=" in their unit file.
For example,
apache2.service has the following under their [Unit] in apache2.service,
"After=network.target remote-fs.target nss-lookup.target"
, this is invalid, as it should rather be::
"After=network.target network-online.target remote-fs.target
nss-lookup.target"
same goes for ssh.service
"After=network.target auditd.service",
should be
"After=network.target network-online.target auditd.service"
and for any other service omitting network-online.target..
. otherwise those services will say "fail" on boot-up.. without any
other further detail.
journactl -xe -u doesn't show any further detail other that the service
failed to "bind" to an address.
^ The ssh service I have set is set to bind to a "specific" interface
that is defined by systemd-networkd's settings in /etc/systemd/network.
(networkctl was shows fully configured interfaces, so there is no issue
happening over here)
The apache2 service is also set to bind to a "specific" interface.
^ By default these services run on 0.0.0.0 -- to run on all interfacaes,
including 127.0.0.1 << which is pretty much ready much earlier. This
explains as to why there is failure when the user defines specified
interfaces later on.
.. whoever is in charge of systemd, should inform other server-package
maintainers to add "network-online.target" as a dependency-check
otherwise those services will fail to start when the user decides to use
specific interfaces.
thanks
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
