Fedora Account System
Red Hat Associate
Red Hat Customer
An strace of the spinning haveged shows this: ``` accept4(0, NULL, NULL, SOCK_CLOEXEC|SOCK_NONBLOCK) = -1 ENOTSOCK (Socket operation on non-socket) pselect6(4, [0], [3], NULL, {tv_sec=2, tv_nsec=0}, {sigmask=[], sigsetsize=8}) = 1 (in [0], left {tv_sec=1, tv_nsec=999999519}) ``` It's doing that in a loop. Downgrading to 1.9.22 resolves the problem. Reproducible: Always Steps to Reproduce: 1.upgrade to new version in updates-testing 2.reboot 3.observe with top Actual Results: 100% CPU Expected Results: normal system operation
Nothing in the journal says anything useful about haveged.
Correction: only ONE message since boot in the log from haveged: Jun 23 22:18:51 fedora haveged[256]: haveged: fills: 1, generated: 512 K bytes, RNDADDENTROPY: 256
FEDORA-2026-28f26f5294 (haveged-1.9.26-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-28f26f5294
FEDORA-2026-5ddd0941a8 (haveged-1.9.26-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-5ddd0941a8
FEDORA-EPEL-2026-e15fb7f042 (haveged-1.9.26-1.el10_2) has been submitted as an update to Fedora EPEL 10.2. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-e15fb7f042
FEDORA-EPEL-2026-e6d245c837 (haveged-1.9.26-1.el10_3) has been submitted as an update to Fedora EPEL 10.3. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-e6d245c837
FEDORA-EPEL-2026-4245f60523 (haveged-1.9.26-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-4245f60523
Thank you for the bug report! Root cause: socket_fd was declared as a global int socket_fd; in havegecmd.c, which defaults to 0. With the new --no-command flag added in v1.9.24, socket initialization is skipped, so socket_fd stays at 0. The daemon loop checks if (socket_fd >= 0) and enters accept4(0, ...), spinning on stdin (fd 0) in a tight loop. Fix (v1.9.26): Initialize socket_fd = -1 so the daemon loop correctly skips the accept path when command mode is disabled. - Upstream release: https://github.com/jirka-h/haveged/releases/tag/v1.9.26 - Bodhi update (F44): https://bodhi.fedoraproject.org/updates/FEDORA-2026-28f26f5294 - Updates also submitted for F43, EPEL 10.2, EPEL 10, and EPEL 9. Could you help to verify the fix once the update appears in updates-testing?
FEDORA-2026-28f26f5294 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-28f26f5294` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-28f26f5294 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-e6d245c837 has been pushed to the Fedora EPEL 10.3 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-e6d245c837 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-4245f60523 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-4245f60523 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-e15fb7f042 has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-e15fb7f042 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-5ddd0941a8 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-5ddd0941a8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-5ddd0941a8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-e15fb7f042 (haveged-1.9.26-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-4245f60523 (haveged-1.9.26-1.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-e6d245c837 (haveged-1.9.26-1.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-5ddd0941a8 (haveged-1.9.26-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-1ffac31a82 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-1ffac31a82` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-1ffac31a82 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
This message is a reminder that Fedora Linux 43 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 43 on 2026-12-02. 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 'version' of '43'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 43 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.