Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#80313 - netplan: hang/deadlock of exatcly 60 seconds whenever a daemon-reload is triggered
Attached to Project:
Arch Linux
Opened by Ville Aakko (Wild_Penguin) - Tuesday, 21 November 2023, 13:56 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 21 November 2023, 22:26 GMT
Opened by Ville Aakko (Wild_Penguin) - Tuesday, 21 November 2023, 13:56 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 21 November 2023, 22:26 GMT
|
DetailsDescription: Whenever netplan and a configuration is in place, systemd daemon-reload of exactly 60 seconds (e.g. more often than not a pacman -Suy is run) will cause a hang (of the daemon-reload process, along with the shell if triggered from a user shell, and most things network-related, and possibly other services?).
As a workaround, I've edited /etc/nsswitch.conf as such: # group: files [SUCCESS=merge] systemd ### netplan bug workaround group: files systemd However, I'm not actually sure what this edit does and what are the possible side-effects. It does remove the hangs. Additional info: * package version netplan-0.107-3 * There is an upstream pull request here for fixing the underlying problem. https://github.com/canonical/netplan/pull/304 * There are bug reports elsewhere, such as here: https://bugs.launchpad.net/netplan/+bug/1999178 Steps to reproduce: - Have a configuration in /etc/netplan. I'm not sure all configs will trigger the bug (as I've understood the bug report, any parseable config will trigger the bug). - Do anything which cases a daemon-reload or trigger it manually. Observed results: - Daemon-reload will take exactly 60 seconds (+ whatever it did originally), during which the system is mostly useless. Expected results: - Daemon-reload should proceed normally in a sensible time frame. |
This task depends upon
Closed by Toolybird (Toolybird)
Tuesday, 21 November 2023, 22:26 GMT
Reason for closing: Upstream
Additional comments about closing: Refer comments
Tuesday, 21 November 2023, 22:26 GMT
Reason for closing: Upstream
Additional comments about closing: Refer comments
---
network:
version: 2
renderer: networkd
bridges:
dummy0:
dhcp4: no
dhcp6: no
accept-ra: no
interfaces: [ ]
addresses:
- 169.254.1.1/32
--- (whitespace lost and no formatting here; this example is from https://serverfault.com/questions/887476/how-do-i-configure-dummy-interface-with-netplan-on-ubunty-17-10)
And then do a systemctl daemon-reload. This is what I observe:
$ time sudo systemctl daemon-reload
real 1m0,707s
user 0m0,004s
sys 0m0,007s
FS#78864.> group: files [SUCCESS=merge] systemd
That bit was added due to
FS#67658.Seeing as this is an upstream bug and not an Arch packaging issue, you could just run with the modified config file until upstream commit a fix. Please continue to liaise with upstream on getting a fix committed.