Bug 14221 - Samba processes killed by the OOM killer don't come back
Summary: Samba processes killed by the OOM killer don't come back
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: 4.11.4
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-18 20:52 UTC by Andrew Bartlett
Modified: 2022-12-08 18:59 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Bartlett 2019-12-18 20:52:01 UTC 
Samba 4.10 and later versions have a process restart capability to greatly reduce the impact of crashes due to a NULL pointer de-reference or abort().

However SIGKILL was deliberatly omitted.  

Sadly this is the most likely case, due to the OOM killer, as raised here:

https://lists.samba.org/archive/samba-technical/2019-November/134529.html

Subsequent discussion (offline) has been to agree that we should restart in this case.
Comment 1 roland 2022-12-08 18:59:51 UTC 
i had smbd killed by oom due to a bug and found no smbd processes running afterwards. 

isn't that systemd's job to restart failed services ?