RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1546658 - systemd stops servicing with "Freezing execution" message upon memory exhaustion [rhel-7.4.z]
Summary: systemd stops servicing with "Freezing execution" message upon memory exhaust...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.3
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Frantisek Sumsal
Marie Hornickova
URL:
Whiteboard:
Depends On: 1437114
Blocks: 1475731
TreeView+ depends on / blocked
 
Reported: 2018-02-19 09:32 UTC by Oneata Mircea Teodor
Modified: 2023-10-06 17:43 UTC (History)
15 users (show)

Fixed In Version: systemd-219-42.el7_4.9
Doc Type: Bug Fix
Doc Text:
If the call of the fork() function failed during the startup of a service, systemd terminated unexpectedly. Consequently, users had to reboot the machine. With this update, systemd has been fixed to print an error message instead of terminating and stopping handling the requests. As a result, systemd keeps working in the described situation.
Clone Of: 1437114
Environment:
Last Closed: 2018-03-06 21:50:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 164837 0 None None None 2019-07-04 12:11:37 UTC
Red Hat Knowledge Base (Solution) 3096191 0 None None None 2018-02-19 09:32:54 UTC
Red Hat Product Errata RHBA-2018:0416 0 normal SHIPPED_LIVE systemd bug fix update 2018-03-07 02:46:04 UTC

Description Oneata Mircea Teodor 2018-02-19 09:32:44 UTC 
This bug has been copied from bug #1437114 and has been proposed to be backported to 7.4 z-stream (EUS).
Comment 12 errata-xmlrpc 2018-03-06 21:50:34 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0416
Note You need to log in before you can comment on or make changes to this bug.