FS#78134 - [systemd] 253.3-2 hangs on reloading device manager configuration
Attached to Project:
Arch Linux
Opened by Dev S (dev) - Thursday, 06 April 2023, 09:06 GMT
Last edited by Christian Hesse (eworm) - Monday, 10 April 2023, 21:37 GMT
Opened by Dev S (dev) - Thursday, 06 April 2023, 09:06 GMT
Last edited by Christian Hesse (eworm) - Monday, 10 April 2023, 21:37 GMT
|
Details
Description:
systemd 253.3-2 installation hangs on reloading device manager configuration Additional info: * package version(s) 253.3-2 Steps to reproduce: # pacman -Syu :: Synchronizing package databases... custom is up to date testing 18.9 KiB 304 KiB/s 00:00 [#############################################################################] 100% core is up to date extra is up to date community-testing is up to date community is up to date :: Starting full system upgrade... resolving dependencies... looking for conflicting packages... Packages (3) systemd-253.3-2 systemd-libs-253.3-2 systemd-sysvcompat-253.3-2 Total Download Size: 8.23 MiB Total Installed Size: 30.80 MiB Net Upgrade Size: 0.00 MiB :: Proceed with installation? [Y/n] :: Retrieving packages... systemd-253.3-2-x86_64 7.2 MiB 39.7 MiB/s 00:00 [#############################################################################] 100% systemd-libs-253.3-2-x86_64 1016.9 KiB 43.2 MiB/s 00:00 [#############################################################################] 100% systemd-sysvcompat-253.3-2-x86_64 5.9 KiB 423 KiB/s 00:00 [#############################################################################] 100% Total (3/3) 8.2 MiB 31.5 MiB/s 00:00 [#############################################################################] 100% (3/3) checking keys in keyring [#############################################################################] 100% (3/3) checking package integrity [#############################################################################] 100% (3/3) loading package files [#############################################################################] 100% (3/3) checking for file conflicts [#############################################################################] 100% (3/3) checking available disk space [#############################################################################] 100% :: Processing package changes... (1/3) upgrading systemd-libs [#############################################################################] 100% (2/3) upgrading systemd [#############################################################################] 100% (3/3) upgrading systemd-sysvcompat [#############################################################################] 100% :: Running post-transaction hooks... ( 1/10) Creating system user accounts... ( 2/10) Updating journal message catalog... ( 3/10) Reloading system manager configuration... ( 4/10) Updating udev hardware database... ( 5/10) Applying kernel sysctl settings... ( 6/10) Creating temporary files... ( 7/10) Reloading device manager configuration... |
This task depends upon
Closed by Christian Hesse (eworm)
Monday, 10 April 2023, 21:37 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 253.3-3
Monday, 10 April 2023, 21:37 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 253.3-3
Because it is most likely this change which introduces the `--settle` option:
https://github.com/archlinux/svntogit-packages/commit/063cdc2311f307f43dadefcf961532f622a18e17
> -w --settle Wait for the triggered events to complete
Maybe also: Do you have any custom udev rules?
This almost always hangs indefinitely for me:
# SYSTEMD_LOG_LEVEL=debug udevadm trigger --settle
sd-device-monitor(n/a): Failed to get the received message size: No buffer space available
^C
Always with that error message.
I can make it not hang most of the time when I test it repeatedly like this:
# udevadm trigger --verbose --dry-run | shuf -n99 | SYSTEMD_LOG_LEVEL=debug xargs udevadm trigger --settle
Then I only occasionally get that same error message, before it hangs:
sd-device-monitor(n/a): Failed to get the received message size: No buffer space available
Maybe a bug in systemd?
Does it make a difference to run `udevadm settle` in a separate command?
FS#78148No hangs when running `udevadm settle` separately.