Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
customer updated RHEL. Straight after update, Winbind is running out of memory.
Applications used are host mail mta and web proxy.
Use samba/ winbind to authenticate with Active directory.
Currently one custoemr uses a cron job to restart winbind every hour or so.
The other customer has done a yum downgrade to the previous working version, which has resolved the issue for them.
Customer Env:
AD RHEL-6.9
All working fine
Updates Whole system.
RHEL-6.9(samba-3.6.23-46.el6_9.x86_64)
# vim gw-smb.conf
[global]
password server = <>
workgroup = <>
realm =
idmap uid = 9999-9999
idmap gid = 9999-9999
winbind reconnect delay = 20
security = ads
<--winbind--
/var/log/messages
Sep 4 11:31:39 <> kernel: : Out of memory: Kill process 27825 (winbindd) score 696 or sacrifice child
Sep 4 11:31:39 <> kernel: : Killed process 27844, UID 0, (winbindd) total-vm:96624kB, anon-rss:312kB, file-rss:388kB
Sep 4 11:31:39 <> kernel: : udisks-daemon invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0
Sep 4 11:31:39 <> kernel: : udisks-daemon cpuset=/ mems_allowed=0
Sep 4 11:31:39 <> kernel: : Pid: 4516, comm: udisks-daemon Not tainted 2.6.32-696.10.1.el6.x86_64 #1
System logs
Sep 4 11:31:49 <> winbindd[27825]: [2017/09/04 11:31:49.553379, 0] winbindd/winbindd_dual.c:1377(fork_domain_child)
Sep 4 11:31:49 <> winbindd[27825]: Could not open child pipe: Too many open files
Version-Release number of selected component (if applicable):
samba-3.6.23-46.el6_9.x86_64
How reproducible:
All time in customer env
Steps to Reproduce:
1.
2.
3.
Actual results:
winbind runs out of memory after upgrade
Expected results:
Winbind should not run out of memory after upgrade
Additional info:
1. Collected valgrind report after running command as:
# valgrind --tool=memcheck --log-file=report.txt --leak-check=full /usr/sbin/winbindd -F
2. Asked customer for providing samba logs at log level=10 at time of issue
Please data provided by customer at:
https://foobar.gsslab.pnq.redhat.com/01936736/
Comment 2Andreas Schneider
2018-03-21 16:36:10 UTC
*** This bug has been marked as a duplicate of bug 1513877 ***
Description of problem: customer updated RHEL. Straight after update, Winbind is running out of memory. Applications used are host mail mta and web proxy. Use samba/ winbind to authenticate with Active directory. Currently one custoemr uses a cron job to restart winbind every hour or so. The other customer has done a yum downgrade to the previous working version, which has resolved the issue for them. Customer Env: AD RHEL-6.9 All working fine Updates Whole system. RHEL-6.9(samba-3.6.23-46.el6_9.x86_64) # vim gw-smb.conf [global] password server = <> workgroup = <> realm = idmap uid = 9999-9999 idmap gid = 9999-9999 winbind reconnect delay = 20 security = ads <--winbind-- /var/log/messages Sep 4 11:31:39 <> kernel: : Out of memory: Kill process 27825 (winbindd) score 696 or sacrifice child Sep 4 11:31:39 <> kernel: : Killed process 27844, UID 0, (winbindd) total-vm:96624kB, anon-rss:312kB, file-rss:388kB Sep 4 11:31:39 <> kernel: : udisks-daemon invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0 Sep 4 11:31:39 <> kernel: : udisks-daemon cpuset=/ mems_allowed=0 Sep 4 11:31:39 <> kernel: : Pid: 4516, comm: udisks-daemon Not tainted 2.6.32-696.10.1.el6.x86_64 #1 System logs Sep 4 11:31:49 <> winbindd[27825]: [2017/09/04 11:31:49.553379, 0] winbindd/winbindd_dual.c:1377(fork_domain_child) Sep 4 11:31:49 <> winbindd[27825]: Could not open child pipe: Too many open files Version-Release number of selected component (if applicable): samba-3.6.23-46.el6_9.x86_64 How reproducible: All time in customer env Steps to Reproduce: 1. 2. 3. Actual results: winbind runs out of memory after upgrade Expected results: Winbind should not run out of memory after upgrade Additional info: 1. Collected valgrind report after running command as: # valgrind --tool=memcheck --log-file=report.txt --leak-check=full /usr/sbin/winbindd -F 2. Asked customer for providing samba logs at log level=10 at time of issue Please data provided by customer at: https://foobar.gsslab.pnq.redhat.com/01936736/