Your message dated Sun, 19 Oct 2025 00:51:08 +0200
with message-id <[email protected]>
and subject line Re: Bug#1118372: apt-daily-upgrade fails when eth0 is not
present
has caused the Debian Bug report #1118372,
regarding apt-daily-upgrade fails when eth0 is not present
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.)
--
1118372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118372
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apt
Version: 3.0.3
I'm running Debian 13.1 Trixie in multiple containers. Last week I
renamed the network devices in the Containers from eth0 to eth60. Since
then can see the following lines in the "/var/log/syslog" of the containers:
2025-10-18T19:36:43+02:00 mojo-proxy systemd[1]: Starting
apt-daily-upgrade.service - Daily apt upgrade and clean activities...
2025-10-18T19:37:13+02:00 mojo-proxy systemd-networkd-wait-online[295
Timeout occurred while waiting for network connectivity.
2025-10-18T19:37:13+02:00 mojo-proxy apt-helper[293]: E: Sub-process
/lib/systemd/systemd-networkd-wait-online returned an error code (1)
2025-10-18T19:37:14+02:00 mojo-proxy systemd[1]:
apt-daily-upgrade.service: Deactivated successfully.
2025-10-18T19:37:14+02:00 mojo-proxy systemd[1]: Finished
apt-daily-upgrade.service - Daily apt upgrade and clean activities.
This Timeout comes from the "apt" package: The
"apt-daily-upgrade.service" calls "ExecStartPre=-/usr/lib/apt/apt-helper
wait-online" which in turn calls
"/usr/lib/systemd/systemd-networkd-wait-online". Which Times out.
The manual[1] of systemds "systemd-networkd-wait-online" clearly states
that by default it only checks eth0. But it also has the parameter
"--interface=" to handle the case when there is no eth0. I successfully
used this Parameter in the "systemd-networkd-wait-online.service" which
had the same problem as the "apt-daily-upgrade.service". Sadly this fix
does not work in the "apt-daily-upgrade.service" case because it does
not call "/usr/bin/systemd/systemd-networkd-wait-online" directly. And
"apt-helper" has no factility in place to hand over the "--interface="
parameter to "systemd-networkd-wait-online".
[1]
https://manpages.debian.org/trixie/systemd/systemd-networkd-wait-online.8.en.html
Best Regards
Fred
--- End Message ---
--- Begin Message ---
On 18 October 2025 20:34:27 CEST, "Frederik Reiß" <[email protected]>
wrote:
>Package: apt
>Version: 3.0.3
>
>
>I'm running Debian 13.1 Trixie in multiple containers. Last week I renamed the
>network devices in the Containers from eth0 to eth60. Since then can see the
>following lines in the "/var/log/syslog" of the containers:
>
>2025-10-18T19:36:43+02:00 mojo-proxy systemd[1]: Starting
>apt-daily-upgrade.service - Daily apt upgrade and clean activities...
>2025-10-18T19:37:13+02:00 mojo-proxy systemd-networkd-wait-online[295 Timeout
>occurred while waiting for network connectivity.
>2025-10-18T19:37:13+02:00 mojo-proxy apt-helper[293]: E: Sub-process
>/lib/systemd/systemd-networkd-wait-online returned an error code (1)
>2025-10-18T19:37:14+02:00 mojo-proxy systemd[1]: apt-daily-upgrade.service:
>Deactivated successfully.
>2025-10-18T19:37:14+02:00 mojo-proxy systemd[1]: Finished
>apt-daily-upgrade.service - Daily apt upgrade and clean activities.
>
>This Timeout comes from the "apt" package: The "apt-daily-upgrade.service"
>calls "ExecStartPre=-/usr/lib/apt/apt-helper wait-online" which in turn calls
>"/usr/lib/systemd/systemd-networkd-wait-online". Which Times out.
>
>The manual[1] of systemds "systemd-networkd-wait-online" clearly states that
>by default it only checks eth0.
This is not true. It states
"by default, it will wait for all links it is aware of and which are managed by
systemd-networkd.service(8) to be fully configured or failed, and for at least
one link to be online"
> But it also has the parameter "--interface=" to handle the case when there is
> no eth0.
No this parameter forces it to wait for a specific inrerface rather than all.
> I successfully used this Parameter in the
> "systemd-networkd-wait-online.service" which had the same problem as the
> "apt-daily-upgrade.service". Sadly this fix does not work in the
> "apt-daily-upgrade.service" case because it does not call
> "/usr/bin/systemd/systemd-networkd-wait-online" directly. And "apt-helper"
> has no factility in place to hand over the "--interface=" parameter to
> "systemd-networkd-wait-online".
Please configure your networks correctly. You have configured networkd to
manage interfaces that are not online during boot which is a problem.
>
>[1]
>https://manpages.debian.org/trixie/systemd/systemd-networkd-wait-online.8.en.html
>
>Best Regards
>
>Fred
--
sent from my phone, excuse the brevity, if any
--- End Message ---
