Bug 1934549

Summary: systemd[1]:Freezing execution after a "systemctl daemon-reexec"
Product: [Fedora] Fedora Reporter: Xose Vazquez Perez <xose.vazquez>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: fedoraproject, filbranden, flepied, kasong, lnykryn, msekleta, ssahani, s, systemd-maint, yuwatana, zbyszek, z
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-05 17:53:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Xose Vazquez Perez 2021-03-03 13:10:13 UTC 
# systemctl daemon-reexec 

Broadcast message from systemd-journald@chuchi (Wed 2021-03-03 11:28:47 CET):

systemd[1]: Caught <ABRT>, dumped core as pid 32873.

chuchi:~ # 
Broadcast message from systemd-journald@chuchi (Wed 2021-03-03 11:28:47 CET):

systemd[1]: Freezing execution.


Message from syslogd@localhost at Mar  3 11:28:47 ...
 systemd[1]:Caught <ABRT>, dumped core as pid 32873.

Message from syslogd@localhost at Mar  3 11:28:47 ...
 systemd[1]:Freezing execution.

------

Fedora 34 (Workstation Edition Prerelease) with systemd-248~rc2-1.fc34.x86_64


Impossible to reboot the OS.
Comment 1 Zbigniew Jędrzejewski-Szmek 2021-03-05 17:53:06 UTC 
It's hard to say anything based on this... Please look in the logs after rebooting.
I'll assume it's the same as #1931034 for now.

*** This bug has been marked as a duplicate of bug 1931034 ***
Comment 2 Xose Vazquez Perez 2021-03-05 17:59:05 UTC 
1 boot the system
2 do "systemctl daemon-reexec"
3 and get a "systemd[1]:Freezing execution."
Comment 3 Zbigniew Jędrzejewski-Szmek 2021-03-05 18:33:32 UTC 
If only things were so simple... Obviously, people are doing daemon-reexec all the time
(it happens at least once during every boot during the transition from initrd to the main
system). But most people are not seeing this error. I test daemon-reexec all the time during development,
but I don't see this crash. So your reproducer is not useful… As I said, if you want this to be resolved,
please check if there's anything interesting in the logs.