Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1546658 - systemd stops servicing with "Freezing execution" message upon memory exhaustion [rhel-7.4.z]
systemd stops servicing with "Freezing execution" message upon memory exhaust...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd (Show other bugs)
7.3
All Linux
urgent Severity urgent
: rc
: ---
Assigned To: systemd-maint
Frantisek Sumsal
Marie Dolezelova
: ZStream
Depends On: 1437114
Blocks: 1475731
  Show dependency treegraph
 
Reported: 2018-02-19 04:32 EST by Oneata Mircea Teodor
Modified: 2018-03-06 16:50 EST (History)
15 users (show)

See Also:
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.
Story Points: ---
Clone Of: 1437114
Environment:
Last Closed: 2018-03-06 16:50:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
IBM Linux Technology Center 164837 None None None 2018-02-19 10:32 EST
Red Hat Knowledge Base (Solution) 3096191 None None None 2018-02-19 04:32 EST
Red Hat Product Errata RHBA-2018:0416 normal SHIPPED_LIVE systemd bug fix update 2018-03-06 21:46:04 EST

  None (edit)
Description Oneata Mircea Teodor 2018-02-19 04:32:44 EST
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 16:50:34 EST
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.