I beg to differ. Yesterday I upgraded my Ubuntu 22.10 to 23.04. That hung many times and took two hours on a machine with a SATA SSD and a Ryzen 7 5700G. Working out some smaller problems I found that systyemctl daemon-reload hangs almost exactly one minute.
Now, this one minute delay is familiar to me. I have it on a Debian 11 machine in the boot sequence. That machine also uses netplan. The timeout seems to occur twice in the boot sequence, causing a delay of two minutes. *But* systemctl daemon-reload is fast on that machine.
Replacing "compat" with "files" on Ubuntu makes no difference.
I had filed a bug report more than a year ago in the Debian bug tracker (#1008995) which went ignored.
So far I have narrowed the problem on Ubuntu 23.04 down to these two lines:
Jul 22 19:45:12 alanya systemd[45294]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator succeeded.
Jul 22 19:46:12 alanya systemd[45294]: /usr/lib/systemd/system-generators/netplan succeeded.
This is from a debug-level journal, you need to change the default level with "systemctl log-level debug" to see them. Default on Ubuntu is "info".
I tried to strace /usr/lib/systemd/system-generators/netplan, but it exited immediately with exit code 1.
If anybody can provide me with a hint on further debugging this, I'm quite willing to continue. Right now, I'm stuck.
Update:
I converted the Debian machine to systemd-networkd and deinstalled the netplan packages. The 2 minute delay remained. The delay is in /lib/systemd/systemd-networkd-wait-online. It waits for any of the network devices. I can make it return immediately by adding a --ignore for all of them. No good option.
But all this is besides the point. The delay on Ubuntu is definitely somewhere in the netplan mechanism.
I beg to differ. Yesterday I upgraded my Ubuntu 22.10 to 23.04. That hung many times and took two hours on a machine with a SATA SSD and a Ryzen 7 5700G. Working out some smaller problems I found that systyemctl daemon-reload hangs almost exactly one minute.
Now, this one minute delay is familiar to me. I have it on a Debian 11 machine in the boot sequence. That machine also uses netplan. The timeout seems to occur twice in the boot sequence, causing a delay of two minutes. *But* systemctl daemon-reload is fast on that machine.
ubuntu-23.04$ grep '^group' /etc/nsswitch.conf
group: compat systemd
debian-11: $ grep '^group' /etc/nsswitch.conf
group: files systemd
Replacing "compat" with "files" on Ubuntu makes no difference.
I had filed a bug report more than a year ago in the Debian bug tracker (#1008995) which went ignored.
So far I have narrowed the problem on Ubuntu 23.04 down to these two lines: systemd/ system- generators/ systemd- gpt-auto- generator succeeded. systemd/ system- generators/ netplan succeeded.
Jul 22 19:45:12 alanya systemd[45294]: /usr/lib/
Jul 22 19:46:12 alanya systemd[45294]: /usr/lib/
This is from a debug-level journal, you need to change the default level with "systemctl log-level debug" to see them. Default on Ubuntu is "info".
I tried to strace /usr/lib/ systemd/ system- generators/ netplan, but it exited immediately with exit code 1.
If anybody can provide me with a hint on further debugging this, I'm quite willing to continue. Right now, I'm stuck.
Update: systemd- networkd- wait-online. It waits for any of the network devices. I can make it return immediately by adding a --ignore for all of them. No good option.
I converted the Debian machine to systemd-networkd and deinstalled the netplan packages. The 2 minute delay remained. The delay is in /lib/systemd/
But all this is besides the point. The delay on Ubuntu is definitely somewhere in the netplan mechanism.