Bug 1332629

Summary:	systemd message says freezing execution
Product:	[Fedora] Fedora	Reporter:	Vivek Goyal <vgoyal>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	dwalsh, johannbg, lnykryn, msekleta, muadda, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-08 14:24:21 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:

Description Vivek Goyal 2016-05-03 15:23:47 UTC

Description of problem:

I am running multiple parallel docker builds on a f24 VM. Few seconds after the build has started, I see following.

Broadcast message from systemd-journald@vm5-f24 (Tue 2016-05-03 11:19:46 EDT):

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


Broadcast message from systemd-journald@vm5-f24 (Tue 2016-05-03 11:19:46 EDT):

systemd[1]: Freezing execution.


Journal has some more info.

May 03 11:19:46 vm5-f24 abrt-hook-ccpp[8212]: Process 1738 (systemd) of user 0 killed by SIGABRT - dumping core
May 03 11:19:46 vm5-f24 abrt-hook-ccpp[8213]: Process 8211 (systemd) of user 0 killed by SIGABRT - ignoring (repeated crash)
May 03 11:19:46 vm5-f24 systemd[1]: Caught <ABRT>, dumped core as pid 8211.
May 03 11:19:46 vm5-f24 systemd[1]: Freezing execution.
May 03 11:19:46 vm5-f24 abrt-hook-ccpp[8210]: Process 1280 (systemd) of user 42 killed by SIGABRT - ignoring (repeated crash)


After that system seems to deteoriate. Docker build seems to be hung after a while or makes very slow progress.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Fedora End Of Life 2017-07-25 20:39:59 UTC

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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.

Comment 2 Fedora End Of Life 2017-08-08 14:24:21 UTC

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.