Created attachment 1719263 [details] Output of systemd-analyze blame (dnf-makecache.service can be ignored) Created attachment 1719263 [details] Output of systemd-analyze blame (dnf-makecache.service can be ignored) Description of problem: Several services starting at boot time take too long to start. These include dracut-initqueue, firewalld, upower, sssd, etc. Version-Release number of selected component (if applicable): systemd.x86 - 246.6-3.fc33 Service provider version numbers are the latest as on 6 Oct 2020 (IST). How reproducible: Always Steps to Reproduce: 1. Do a cold boot. 2. Check the output of systemd-analyze blame Actual results: The topmost services take too long (more than ~ 5-6 secs) to start. firewalld.service blocks for about 6-7 secs. If it is disabled, upower takes about the same time. This adds about 7 seconds to the boot time (see systemd-analyze critical-chain - the blocking approximately doubles the start-up time). A warm (re)boot takes even longer. Expected results: Critical system services should not take so long to start, blocking and increasing the start-up time. Additional info: The system has LUKS2-encrypted partitions with manual password entry, which is why cryptsetup takes long, but that is reasonable and acceptable. lvm, lvmmerge, iscsi, multipath, mdraid, md, dmraid, qemu, qemu-net, virtfs, livesys, and livesys-late are disabled in the GRUB configuration (disabling these in the dracut configuration makes no difference). Related systemd services are also disabled/masked. plymouth-quit-wait is also masked (enabling it makes the start-up time even longer). /var/log/journal/ has been deleted so that the journal is created on tmpfs /run/log/journal/ .
The affected system is Fedora Workstation 33 Pre-release Edition (33 Beta), running the default GNOME 3.38 desktop environment.
Created attachment 1719300 [details] Second cold boot output of systemd-analyze blame Attached another (usual case) output of systemd-analyze blame . It can be seen that dracut-initqueue, firewalld, upower, and sssd are taking a significant amount of time. I know that these do run in parallel, but any one of them blocking adds that time period to the start-up time, which is my primary concern here. Also, e.g., if I disable firewalld, upower will block in its place.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.