Got it on mantic -> noble upgrade too, the solution proposed in the Description
helped:
$ systemctl disable --now systemd-networkd.service
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Got it on mantic -> noble upgrade too, the solution proposed in the Description
helped:
$ systemctl disable --now systemd-networkd.service
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hi,
I got hit by this bug after a mantic -> noble upgrade on a desktop system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358
Title:
systemd wait-online now times
I have a number of RPi installed with Ubuntu Server 23.10 (64 bit)
installations in Nov. 2023. They do no have this problem. Installing the
same OS about a week ago on the same RPi, causes the problem. So the
problem was likely caused by something Ubuntu released between Nov. to
March.
@Steve
> If you have a bunch of unmanaged interfaces, then you should use a
> drop-in configuration to pass the --any flag to
> systemd-networkd-wait-online:
>
> cat > /etc/systemd/system/systemd-networkd-wait-online.service.d/any.conf <<
> EOF
> [Service]
> ExecStart=
>
There is no workaround for this with the stock netplan config on
raspberry pi, which trips this bug. But you can customize /etc/netplan/
on your system to mark your expected/required network interfaces as
"optional: false" (which is the default if unspecified); AIUI that would
avoid this issue
I've reported the same reproducible issue on Raspberry Pi troubleshooting forum
with Ubuntu 22.04.3 LTS 64-bit server as I was not aware of this bugreport:
https://forums.raspberrypi.com/viewtopic.php?p=2172165
> systemctl disable --now systemd-networkd.service
This does not work for me as the
Indeed. I would have preferred to remain on LTS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358
Title:
systemd wait-online now times out after jammy and lunar
So you eventually upgraded both raspis to 23.10? I find it hardly
surprising it works as mantic has a newer upstream release of systemd
253.5 which has the fix I linked to above for ignoring unmanaged
interfaces. Does not help for the LTS release (jammy) though.
--
You received this bug
My shotgun approach may seem unorthodox but I've been frustrated since I
am confident the systemd update created this issue. However, I withdraw
my hesitation to use the word arbitrary. :D
Data point 1: Imaged a vanilla RPI4 with Ubuntu 22.04. The only thing I
changed was the netplan config to
If you have a bunch of unmanaged interfaces, then you should use a drop-
in configuration to pass the --any flag to systemd-networkd-wait-online:
cat > /etc/systemd/system/systemd-networkd-wait-online.service.d/any.conf << EOF
[Service]
ExecStart=
I encountered the same problem after an update as well.
The upstream issue I linked to, although quite old, discusses systemd
version 252.3, whereas at least jammy has a patched version of 249.11.
And you do have e.g. wlan0 unmanaged as do I, which alone causes the
timeout for me.
--
You
Thank you Veli-Jussi for your comment and providing this information. It
appears this or similar problem has been around for a while but as I
stated in my earlier post I only encountered this timeout issue after
the update and it still exists in 249.11-0ubuntu3.11. After the dreaded
timeout (and
I would not be surprised if your issue was at least related as you have
a bunch of unconfigured interfaces. As far as I understand, the fix
discussed here only addresses the case when an interface is marked as
optional. However, the same timeout occurs also for UNMANAGED interfaces
- a behavior
Thank you Steve, perhaps you are right and unrelated. I will open a
separate bug. What confused me (still) is why systemd-wait-
online.service fails same/similar???
sudo systemctl status systemd-networkd-wait-online.service
× systemd-networkd-wait-online.service - Wait for Network to be
On Sun, Dec 10, 2023 at 01:45:36AM -, Roger Nelson wrote:
> I'm curious if this bug is still being investigated. RPI4 with wlan0,
> eth0 and eth1 (USB3 using r8152 driver) definitely manifests this bug. I
> need to wait ~30 minutes before either wlan0 or eth0 becomes available
> in order to
I'm curious if this bug is still being investigated. RPI4 with wlan0,
eth0 and eth1 (USB3 using r8152 driver) definitely manifests this bug. I
need to wait ~30 minutes before either wlan0 or eth0 becomes available
in order to restart systemd-networkd to activate eth1 and then ip link
set up eth1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358
Title:
systemd wait-online now times out after jammy and lunar upgrade
Status in systemd package in Ubuntu:
This is indeed still broken. Running on Raspberry Pi 4 ubuntu-server
image.
# dpkg -l systemd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
This bug should be reopened.
The issue "A start job is running for Wait For Network to be Configured
hanging at boot for 2 minutes in Ubuntu 22.04 servers" for me on Ubuntu
22.04 serverThe timeout error still happens even after installing the
stable release update.
--
You received this bug
I wish I was in the office as little as Herr Schmidt!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358
Title:
systemd wait-online now times out after jammy and
I think this bug should be reopened.
The timeout error still happens even after installing the stable release
update.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358
systemd 249.11-0ubuntu3.11 bug still exists
root@ubuntu:~# netplan get
network:
version: 2
renderer: networkd
ethernets:
eth0:
dhcp4: true
optional: true
dhcp-identifier: "mac"
root@ubuntu:~# networkctl list
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback
I'm now seeing a workable version of systemd available (but kept back?)
on my 22.04 LTS systems without having to enasble proposed on them. This
version (249.11-0ubuntu3.11) addresses the long boot problem, but I've
had to tell apt directly to install systemd to trigger the update. For
anyone who
This bug was fixed in the package systemd - 252.5-2ubuntu3.2
---
systemd (252.5-2ubuntu3.2) lunar; urgency=medium
* wait-online: exit early if all links are ignored (LP: #2036358)
File:
debian/patches/lp2036358-wait-online-exit-early-if-all-links-are-ignored.patch
This bug was fixed in the package systemd - 249.11-0ubuntu3.11
---
systemd (249.11-0ubuntu3.11) jammy; urgency=medium
* wait-online: exit early if all links are ignored (LP: #2036358)
File:
debian/patches/lp2036358-wait-online-exit-early-if-all-links-are-ignored.patch
systemd "249.11-0ubuntu3.11" "fixed" it for me, thanks to those posting
the solution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358
Title:
systemd wait-online
Chris, Andreas, SRU team - In short, I think this should be released to
-updates, yes. From looking through the various comments I have observed
the same that either (a) a user is not testing with -proposed, or (b)
they are in a slightly different situation (but see the timeout
nonetheless, hence
systemd 249.11-0ubuntu3.11 does *not* solve the issue for me. I seem to
be running into the same situation as Werner in #32 where `optional:
true` from the netplan config is not being respected.
systemd-networkd-wait-online seems to ignore `RequiredForOnline=no` in
the .network config.
Netplan
Currently experiencing the same issue as @wharnisch2 on ubuntu 22.04.3
5.15.0-86-generic with systemd 249 (249.11-0ubuntu3.10) on a somewhat
fresh install (few weeks old)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hi @enr0n, could you please comment on Chris's remark above about the
state of this SRU?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358
Title:
systemd wait-online
I just upgraded a core system from Ubuntu 18.04->20.04->22.04, and this
is somehow the only system that has this 2minute + wait bug.
How exactly was this not handled automatically in the upgrade process
for 20.04->22.04? Isn't that the whole point of that automation?
I'm not entirely sure right
(SRU team member): It's not entirely clear to me what the status of this
bug is? It's marked as verification-done and all the autopkgtests are
clear, but there's a lot of “it doesn't work” chatter. Let's see if I
can summarise:
Werner seems to be seeing a hanging problem with 249.11-0ubuntu3.11.
This introduces an unacceptable regression on Raspberry Pis. An
interface that is *not* listed must not cause a 2 min timeout.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I'm having the same effect like Werner. On a vm with jammy server, plain
install - after an update today systemd-networkd delays booting. After
removing the "optional: true" statement, the boot behaviour is normal.
Strange enough, thought this statement should do just the opposite.
--
You
@Nick
think I managed to get 'debug level output from systemd-networkd-wait-
online' with a little help from a friend:
Oct 8 10:00:42 idefix systemd-networkd-wait-online[676]: Found link 4
Oct 8 10:00:42 idefix systemd-networkd-wait-online[676]: Found link 3
Oct 8 10:00:42 idefix
@Nick
this is the syslogd output:
Oct 8 09:33:37 idefix systemd-networkd-wait-online[668]: Timeout occurred
while waiting for network connectivity.
Oct 8 09:33:37 idefix systemd[1]: systemd-networkd-wait-online.service: Main
process exited, code=exited, status=1/FAILURE
Oct 8 09:33:37
Werner - it sounds like you might have been having a different issue.
Without the debug level output from systemd-networkd-wait-online, it's
hard to tell what caused the timeout. Glad you have a workaround,
though.
--
You received this bug notification because you are a member of Ubuntu
Touch
Workaround is to remove "optional: true" from netplan settings, in this
case the issue does not occur.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358
Title:
Did the update via jammy-proposed. Sorry, but 249.11-0ubuntu3.11 does
NOT fix the issue of "A start job is running for Wait For Network to be
Configured hanging at boot for 2 minutes in Ubuntu 22.04 servers" for me
on Ubuntu 22.04 server.
--
You received this bug notification because you are a
Dave - yeah that's the expect outcome with this patch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358
Title:
systemd wait-online now times out after jammy and
Dave - This happens to me on Pi as well. I have wlan0 fully disabled, so
that doesn't appear to be the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358
Title:
Seeing the same results as comment 27 with the Pi lunar (23.04) image.
After installing -proposed and checking systemd-networkd-wait-online,
with wlan0 undefined in the netplan configuration (but eth0 set as the
default DHCP and optional), it still waits for the full 2 minutes,
presumably because
I believe the remaining autopkgtest failures are unrelated.
For lunar[1], we have ubuntu-drivers-common failing on ppc64el[2]. We
can see the same failure on a different test run without a systemd
trigger[3].
For jammy[4], we have linux-nvidia[5] and linux-nvidia-tegra-igx[6],
each failing
Hi folks,
I landed here while investigating issues running Ubuntu 22.04 (Jammy) on
WSL2. I tested the proposed version and have mixed results.
NetworkManager is not installed. systemd-network is enabled, but I don't
know if WSL actually uses it.
Like 249.11-0ubuntu3.10, 249.11-0ubuntu3.11 also
Tested 249.11-0ubuntu3.11 on Ubuntu Server 22.04 (Jammy) and now I have no
delay on boot.
Also the following command now returns immediately:
$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10
Found link 9
Found link 8
Found link 7
Found link 6
Found link 5
Found
It is not a typical configuration to have both services running.
It makes sense to have both services running, IF you have configured
separate network interfaces to be managed by each. But this is a very
uncommon configuration.
The expectation is that the services are dynamically enabled only
re: "you should not have both services running"
Is this documented somewhere? What software or script, during system
installation, is meant to ensure this? I have not seen warnings emitted
from postinst (as added for /etc/network/interfaces) or service start.
--
You received this bug
Thanks for the tip. Not sure why both were enabled but disabling
systemd-networkd.service fixes the long wait during boot for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
[NOTE]
If you are running a desktop system and you see this issue, you should
run:
$ systemctl disable --now systemd-networkd.service
This will disable systemd-networkd and associated units, including
systemd-networkd-wait-online.service.
I have verified the fix using systemd 249.11-0ubuntu3.11 from jammy-
proposed:
Creating a fresh container:
nr@six:~$ lxc launch ubuntu-daily:jammy jammy
Creating jammy
Starting jammy
nr@six:~$ lxc exec jammy bash
Within the container, after enabling -proposed:
I have verified the fix using systemd 252.5-2ubuntu3.2 in lunar-
proposed:
Creating a fresh container:
nr@six:~$ lxc launch ubuntu-daily:lunar lunar
Creating lunar
Starting lunar
nr@six:~$ lxc exec lunar bash
In the container, after enabling -proposed:
** Description changed:
[NOTE]
If you are running a desktop system and you see this issue, you should
run:
$ systemctl disable --now systemd-networkd.service
This will disable systemd-networkd and associated units, including
systemd-networkd-wait-online.service.
Tais - you should not have both services running. For you the solution
should be:
$ systemctl disable --now systemd-networkd.service
This will also disable associated units, including systemd-networkd-
wait-online.service.
** Description changed:
+ [NOTE]
+
+ If you are running a desktop
Tested 252.5-2ubuntu3.2 on Ubuntu 23.04 (lunar) and it still hangs for 2
minutes during boot.
$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10
Found link 7
Found link 6
Found link 5
Found link 4
Found link 3
Found link 2
Found link 1
lo: link is ignored
wlp6s0:
Robert - are you on on desktop or server? If the links are not managed
by systemd-networkd, it seems like you would be running NetworkManager?
What does this show for you?
$ systemctl status systemd-networkd
$ systemctl status NetworkManager
--
You received this bug notification because you are
Tested 249.11-0ubuntu3.11 on Ubuntu 22.04 (jammy) and system still wait
for network to be configured
$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10
Found link 3
Found link 2
Found link 1
enp2s0: link is not managed by networkd (yet?).
wlp3s0: link is not managed
Tested 249.11-0ubuntu3.11 on Ubuntu 22.04 (jammy) for riscv64 (HiFive
Unmatched). The system now boots normally.
$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10
rtnl: message parse - overwriting repeated attribute
Found link 2
Found link 1
eth0: link is ignored
Thank you everyone for your speedy work! I have verified
"249.11-0ubuntu3.11" fixes the issue on Jammy for me! Very much
appreciated.
Steps taken:
# 1)
cat
Hello Jamie, or anyone else affected,
Accepted systemd into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/252.5-2ubuntu3.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This behavior is not present in Mantic, so nothing to do there. I have
staged fixes for Jammy and Lunar.
** Changed in: systemd (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Lunar)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu)
** Description changed:
[Impact]
- When all interfaces "not required for online", e.g. when they are marked
- "optional: true" in netplan, systemd-networkd-wait-online will timeout.
- Or, in other words, systemd-networkd-wait-online will timeout even
- though all interfaces are ignored,
** Description changed:
+ [Impact]
+
+ When all interfaces "not required for online", e.g. when they are marked
+ "optional: true" in netplan, systemd-networkd-wait-online will timeout.
+ Or, in other words, systemd-networkd-wait-online will timeout even
+ though all interfaces are ignored,
I will work on re-instating the previous patch in some fashion to fix
this bug without regressing 1982218.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358
Title:
** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
** Also affects: systemd (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Jammy)
Status: New =>
It also affects Ubuntu Server 22.04 after updating to 249.11-0ubuntu3.10, since
I'm on a headless server, I'm not using NetworkManager.
On boot systemd-networkd-wait-online hangs and fails after a timeout.
Here's my netplan configuration:
$ cat /etc/netplan/00-installer-config.yaml
# This
> If you are using NetworkManager, then systemd-networkd.service (and
associated units like systemd-networkd-wait-online.service) should NOT
be enabled. With the caveat that I am not sure why you have systemd-
networkd enabled in the first place, I would recommend that you simply
disable it:
> $
>> On Ubuntu 22.04 desktop system using network-manager
> To be clear, does this mean you have no network interfaces that are
configured to use networkd?
Hey Steve :)
So, this system is quite old. I think the first install was 16.04 and it
went through a bunch of upgrades (mostly interim until
I'm also affected by this: I'm on Ubuntu 22.04.3 for Raspberry Pi and
after updating to 249.11-0ubuntu3.10 on boot I get:
Sep 18 19:16:33 pi4-ubuntu systemd[1]: Starting Wait for Network to be
Configured...
Sep 18 19:19:29 pi4-ubuntu systemd-networkd-wait-online[1319]: Timeout occurred
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Also appears to be affecting the Pi server images (which have no network
manager and only use networkd for networking); I've only checked lunar
so far.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
If you are using NetworkManager, then systemd-networkd.service (and
associated units like systemd-networkd-wait-online.service) should NOT
be enabled. With the caveat that I am not sure why you have systemd-
networkd enabled in the first place, I would recommend that you simply
disable it:
$
> On Ubuntu 22.04 desktop system using network-manager
To be clear, does this mean you have no network interfaces that are
configured to use networkd?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
On Ubuntu 22.04 desktop system using network-manager and upgrading to
systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
- logins (GDM, ssh, console) until it does. This seems to be introduced by
- the change for
+ logins (GDM, ssh, console) until it
** Changed in: systemd (Ubuntu)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
75 matches
Mail list logo
