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.
DescriptionDariusz Wojewódzki
2017-07-05 09:20:01 UTC
Description of problem:
I would like to request the backport of the following fix to samba-winbind-3.6 as per
https://attachments.samba.org/attachment.cgi?id=10128
and https://bugzilla.samba.org/show_bug.cgi?id=3204
Version-Release number of selected component (if applicable):
This is missed for the RHEL6 branch.
Please asses the possibility to integrate patch on RHEL 6.X Line.
How reproducible:
Steps to Reproduce:
(for unknown reason) winbind __does not close sockets__
Here what scenario looks like (on actual production system, as mentioned before we are not able to reproduce it):
At some point in time following messages appears (this looks like random, no apparent issues are reported by OS before):
May 1 11:03:27 zc01.zone1 winbindd[5556]: [2017/05/01 11:03:27.380063, 0] winbindd/winbindd.c:975(winbindd_listen_fde_handler)
May 1 11:03:27 zc01.zone1 winbindd[5556]: winbindd: Exceeding 200 client connections, no idle connection found
May 1 11:03:27 zc01.zone1 winbindd[5556]: [2017/05/01 11:03:27.388117, 0] winbindd/winbindd.c:975(winbindd_listen_fde_handler)
May 1 11:03:27 zc01.zone1 winbindd[5556]: winbindd: Exceeding 200 client connections, no idle connection found
May 1 11:03:32 zc01.zone1 winbindd[5556]: [2017/05/01 11:03:32.119143, 0] winbindd/winbindd.c:975(winbindd_listen_fde_handler)
May 1 11:03:32 zc01.zone1 winbindd[5556]: winbindd: Exceeding 200 client connections, no idle connection found
May 1 11:03:32 zc01.zone1 winbindd[5556]: [2017/05/01 11:03:32.119528, 0] winbindd/winbindd.c:975(winbindd_listen_fde_handler)
May 1 11:03:32 zc01.zone1 winbindd[5556]: winbindd: Exceeding 200 client connections, no idle connection found
(...)
Winbind will stay at this state for some time, but after an hour or so process runs out of descriptors and message flood begins (this means like 10000+ entries/s), with following logs:
May 1 12:19:31 zc01.zone1 winbindd[5556]: winbindd: Exceeding 200 client connections, no idle connection found
May 1 12:19:32 zc01.zone1 winbindd[5556]: [2017/05/01 12:19:32.468367, 0] winbindd/winbindd.c:975(winbindd_listen_fde_handler)
May 1 12:19:32 zc01.zone1 winbindd[5556]: winbindd: Exceeding 200 client connections, no idle connection found
May 1 12:19:32 zc01.zone1 winbindd[5556]: [2017/05/01 12:19:32.468437, 0] winbindd/winbindd.c:817(new_connection)
May 1 12:19:32 zc01.zone1 winbindd[5556]: Faild to accept socket - Too many open files
May 1 12:19:32 zc01.zone1 winbindd[5556]: [2017/05/01 12:19:32.468608, 0] winbindd/winbindd.c:975(winbindd_listen_fde_handler)
May 1 12:19:32 zc01.zone1 winbindd[5556]: winbindd: Exceeding 200 client connections, no idle connection found
May 1 12:19:32 zc01.zone1 winbindd[5556]: [2017/05/01 12:19:32.468630, 0] winbindd/winbindd.c:817(new_connection)
May 1 12:19:32 zc01.zone1 winbindd[5556]: Faild to accept socket - Too many open files
May 1 12:19:32 zc01.zone1 winbindd[5556]: [2017/05/01 12:19:32.468685, 0] winbindd/winbindd.c:975(winbindd_listen_fde_handler)
May 1 12:19:32 zc01.zone1 winbindd[5556]: winbindd: Exceeding 200 client connections, no idle connection found
May 1 12:19:32 zc01.zone1 winbindd[5556]: [2017/05/01 12:19:32.468704, 0] winbindd/winbindd.c:817(new_connection)
May 1 12:19:32 zc01.zone1 winbindd[5556]: Faild to accept socket - Too many open files
Actual results:
This of course provides huge impact on I/O, /var/log gets full in the matter of minutes and process itself eating up CPU making server so busy it's impossible to login on console or ssh. To recover the server you need to power-cycle & do some clean up on /var/log.
Expected results:
Additional info:
Comment 3Andreas Schneider
2017-07-18 09:14:01 UTC
*** This bug has been marked as a duplicate of bug 1467395 ***