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:
Some customer after not getting "wbinfo -u" output in samba versionsamba-4.2.10-6.el7_2.x86_64. The command is failing with error below.
---------------------------------------------------------------------------
2016/05/27 10:08:53.558326, 1, pid=1247, effective(0, 0), real(0, 0)] ../librpc/ndr/ndr.c:439(ndr_print_function_debug)
wbint_QueryUserList: struct wbint_QueryUserList
out: struct wbint_QueryUserList
users : *
users: struct wbint_userinfos
num_userinfos : 0x00000000 (0)
userinfos: ARRAY(0)
result : NT_STATUS_IO_TIMEOUT
[2016/05/27 10:08:53.558426, 10, pid=1247, effective(0, 0), real(0, 0), class=winbind] ../source3/winbindd/winbindd_list_users.c:128(winbindd_list_users_done)
Domain CORP returned 0 users
[2016/05/27 10:08:53.558459, 10, pid=1247, effective(0, 0), real(0, 0), class=winbind] ../source3/winbindd/winbindd_list_users.c:134(winbindd_list_users_done)
List_users for domain EXAMPLE failed
[2016/05/27 10:08:53.558482, 10, pid=1247, effective(0, 0), real(0, 0), class=winbind] ../source3/winbindd/winbindd.c:787(wb_request_done)
wb_request_done[1461:LIST_USERS]: NT_STATUS_OK
[2016/05/27 10:08:53.558537, 10, pid=1247, effective(0, 0), real(0, 0), class=winbind] ../source3/winbindd/winbindd.c:851(winbind_client_response_written)
winbind_client_response_written[1461:LIST_USERS]: delivered response to client
[2016/05/27 10:08:53.558703, 6, pid=1247, effective(0, 0), real(0, 0), class=winbind] ../source3/winbindd/winbindd.c:957(winbind_client_request_read)
closing socket 28, client exited
---------------------------------------------------------------------------
At the same time, "wbinfo -g" command is working properly.
Downgrading to version samba-4.2.3-12.el7_2.x86_64 resolves the issue.
Version-Release number of selected component (if applicable):
samba-4.2.10-6.el7_2.x86_64
How reproducible:
Always by customer.
Steps to Reproduce:
1. /etc/samba/smb.conf
----------------------------------------------------------------------------
[global]
workgroup = EXAMPLE
netbios name = rhel7v2
server string = rhel7v2
dns proxy = no
security = ads
browsable = yes
realm = EXAMPLE.COM
encrypt passwords = true
passdb backend = tdbsam
obey pam restrictions = yes
invalid users = root
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .
log file = /var/log/samba/log.%m
syslog = 0
panic action = /usr/share/samba/panic-action %d
log level = 10
debug pid = true
debug timestamp = yes
max log size = 0
socket options = TCP_NODELAY
interfaces = 191.168.0.2
bind interfaces only = yes
printcap name = /dev/null
load printers = no
printing = bsd
----------------------------------------------------------------------------
2. Join with AD
3. Start winbind service.
4. wbinfo -u
Actual results:
wbinfo -u is not displaying any error.
Expected results:
wbinfo -u should display user information.
Additional info:
Comment 4Andreas Schneider
2016-06-20 14:09:56 UTC
Against which Windows Server version is this?
Could you try if it works setting: 'allow wrapped messages up to a size' in the [global] section of the smb.conf?
Comment 5Andreas Schneider
2016-06-20 15:07:45 UTC
Sorry. I meant: 'client ldap sasl wrapping = plain'
Comment 6Andreas Schneider
2016-06-20 15:09:08 UTC
If this doesn't work, then please try: 'winbind rpc only = yes'
Comment 7Andreas Schneider
2016-06-21 06:06:27 UTC
Let me know which of the two options work. Thanks.
Comment 8Andreas Schneider
2016-06-21 08:09:29 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://rhn.redhat.com/errata/RHBA-2016-2468.html
Description of problem: Some customer after not getting "wbinfo -u" output in samba versionsamba-4.2.10-6.el7_2.x86_64. The command is failing with error below. --------------------------------------------------------------------------- 2016/05/27 10:08:53.558326, 1, pid=1247, effective(0, 0), real(0, 0)] ../librpc/ndr/ndr.c:439(ndr_print_function_debug) wbint_QueryUserList: struct wbint_QueryUserList out: struct wbint_QueryUserList users : * users: struct wbint_userinfos num_userinfos : 0x00000000 (0) userinfos: ARRAY(0) result : NT_STATUS_IO_TIMEOUT [2016/05/27 10:08:53.558426, 10, pid=1247, effective(0, 0), real(0, 0), class=winbind] ../source3/winbindd/winbindd_list_users.c:128(winbindd_list_users_done) Domain CORP returned 0 users [2016/05/27 10:08:53.558459, 10, pid=1247, effective(0, 0), real(0, 0), class=winbind] ../source3/winbindd/winbindd_list_users.c:134(winbindd_list_users_done) List_users for domain EXAMPLE failed [2016/05/27 10:08:53.558482, 10, pid=1247, effective(0, 0), real(0, 0), class=winbind] ../source3/winbindd/winbindd.c:787(wb_request_done) wb_request_done[1461:LIST_USERS]: NT_STATUS_OK [2016/05/27 10:08:53.558537, 10, pid=1247, effective(0, 0), real(0, 0), class=winbind] ../source3/winbindd/winbindd.c:851(winbind_client_response_written) winbind_client_response_written[1461:LIST_USERS]: delivered response to client [2016/05/27 10:08:53.558703, 6, pid=1247, effective(0, 0), real(0, 0), class=winbind] ../source3/winbindd/winbindd.c:957(winbind_client_request_read) closing socket 28, client exited --------------------------------------------------------------------------- At the same time, "wbinfo -g" command is working properly. Downgrading to version samba-4.2.3-12.el7_2.x86_64 resolves the issue. Version-Release number of selected component (if applicable): samba-4.2.10-6.el7_2.x86_64 How reproducible: Always by customer. Steps to Reproduce: 1. /etc/samba/smb.conf ---------------------------------------------------------------------------- [global] workgroup = EXAMPLE netbios name = rhel7v2 server string = rhel7v2 dns proxy = no security = ads browsable = yes realm = EXAMPLE.COM encrypt passwords = true passdb backend = tdbsam obey pam restrictions = yes invalid users = root passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* . log file = /var/log/samba/log.%m syslog = 0 panic action = /usr/share/samba/panic-action %d log level = 10 debug pid = true debug timestamp = yes max log size = 0 socket options = TCP_NODELAY interfaces = 191.168.0.2 bind interfaces only = yes printcap name = /dev/null load printers = no printing = bsd ---------------------------------------------------------------------------- 2. Join with AD 3. Start winbind service. 4. wbinfo -u Actual results: wbinfo -u is not displaying any error. Expected results: wbinfo -u should display user information. Additional info: