Description of problem: when I try run systemd-analyze show some fail(unit service is changing time to time) [martin@localhost SOURCES]$ sudo systemd-analyze blame [sudo] heslo pro martin: Failed to get timestamp properties of unit nftables.service: Spojení bylo příliš dlouho neaktivní after that sudo take too long or fail, sometimes system freeze Version-Release number of selected component (if applicable): systemd-246.1-1.fc33.x86_64 sudo-1.9.1-3.fc33.x86_64 How reproducible: often Steps to Reproduce: 1.run systemd-analyze blame 2.try something else (sudo dnf update, run game in steam ...) 3.system freeze or command fail/take too long when is something do Actual results: system got fail after systemd-analyze blame Expected results: system running ok Additional info:
Created attachment 1712402 [details] journalctl -o short-unix --no-hostname -b
Can confirm this. After doing 'systemd-analyze blame' system dying. Can't even reboot. ❯ systemd-analyze blame Failed to get timestamp properties of unit sys-devices-pci0000:00-0000:00:11.0-ata4-host3-target3:0:0-3:0:0:0-block-sdb.device: Connection timed out Version-Release number of selected component (if applicable): systemd-246.1-1.fc33.x86_64
I set "timedatectl set-local-rtc 0" now is working
After some upstream discussion we found one suspicious patch. In https://copr.fedorainfracloud.org/coprs/zbyszek/systemd/build/1635482/ there's build systemd-246.3-2 that reverts the patch. It is otherwise the same as systemd-246.3-1 in rawhide/f33 right now. It would be great if someone who can reproduce the issue checked whether it still occurs with systemd-246.3-2. (And if *not*, then whether it still occurs with systemd-246.3-1.)
(In reply to Zbigniew Jędrzejewski-Szmek from comment #4) > https://copr.fedorainfracloud.org/coprs/zbyszek/systemd/build/1635482/ This requires rebuilt i guess? Please check copr build and i'll test it. Also tried 'systemd-246.3-1' but issue is still here, yep.
with systemd-246.3-1 has the same behavior, fail with "RTC in local TZ: YES"(fc33 default) ,works ok with "RTC in local TZ: NO"
Sorry for that. https://copr.fedorainfracloud.org/coprs/zbyszek/systemd/build/1635567/ is the replacement for https://copr.fedorainfracloud.org/coprs/zbyszek/systemd/build/1635482/.
(In reply to Martin from comment #6) > with systemd-246.3-1 has the same behavior, fail with "RTC in local TZ: > YES"(fc33 default) ,works ok with "RTC in local TZ: NO" Hmm, OK. So maybe it's that we load with a wrong time, store the mtime, and keep trying to load the unit because we think the modification time is in the future.
systemd-246.3-2 behavior just flipped sytem dies if "RTC in local TZ: NO" and works "wellL" with "RTC in local TZ: YES"
just in case if someone try reproduce. Virtual Machine(KVM efi) is not affected, just bare metal (for me).
Tested and unfortunately issue is still here in 'systemd-246.3-2'.
(In reply to Zbigniew Jędrzejewski-Szmek from comment #8) > (In reply to Martin from comment #6) > > with systemd-246.3-1 has the same behavior, fail with "RTC in local TZ: > > YES"(fc33 default) ,works ok with "RTC in local TZ: NO" > > Hmm, OK. So maybe it's that we load with a wrong time, store the mtime, and > keep trying to load > the unit because we think the modification time is in the future. If its related,not sure with systemd-246.3-2 show chronyd[809]: System clock wrong by 7200.644458 seconds, adjustment started chronyd[809]: System clock was stepped by 7200.644458 seconds
FEDORA-2020-2255b438a2 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-2255b438a2
systemd-246.4-1.fc33.x86_64 looks works ok now
FEDORA-2020-2255b438a2 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-2255b438a2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-2255b438a2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-2255b438a2 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.