Bug 10600 - sam_sid_to_name: possible deadlock
sam_sid_to_name: possible deadlock
Status: NEEDINFO
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services
4.1.7
All FreeBSD
: P5 normal
: ---
Assigned To: Samba QA Contact
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-05-08 22:24 UTC by Josh Paetzel
Modified: 2016-07-29 03:37 UTC (History)
2 users (show)

See Also:


Attachments
Syslog of Freenas 9.2.1.6 beta (103.48 KB, text/plain)
2014-05-23 18:51 UTC, Craig Schappacher
no flags Details
I was able to make changes to the smb4.conf file. (183.11 KB, text/plain)
2014-05-27 12:49 UTC, Craig Schappacher
no flags Details
I was able to restart winbindd and generate a new log. (72.38 KB, text/plain)
2014-05-27 19:00 UTC, Craig Schappacher
no flags Details
Error happened @ 4:11 (1.39 MB, application/octet-stream)
2014-05-27 20:20 UTC, Craig Schappacher
no flags Details
Error happened @ 4:11 (2.42 KB, application/octet-stream)
2014-05-27 20:21 UTC, Craig Schappacher
no flags Details
Error happened @ 4:11 (8.35 KB, application/octet-stream)
2014-05-27 20:22 UTC, Craig Schappacher
no flags Details
Attachment to https://bugzilla.samba.org/show_bug.cgi?id=10600#c14 (686.86 KB, application/x-zip-compressed)
2014-06-24 11:14 UTC, Joerg Altendorf
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Paetzel 2014-05-08 22:24:48 UTC
Apr 18 10:27:37 freenas winbindd2029: [2014/04/18 10:27:37.190839, 0] ../source3/winbindd/winbindd_samr.c:694(sam_sid_to_name)
Apr 18 10:27:37 freenas winbindd2029: sam_sid_to_name: possible deadlock - trying to lookup SID S-1-5-21-2618753002-2285421134-873032427-1000

I ran the following command
wbinfo -s S-1-5-21-2618753002-2285421134-873032427-1000

[root@freenas ~]# wbinfo -s S-1-5-21-2618753002-2285421134-873032427-1000 
failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND 
Could not lookup sid S-1-5-21-2618753002-2285421134-873032427-1000

https://bugs.freenas.org/issues/4432#change-19535
Comment 1 Josh Paetzel 2014-05-23 17:25:54 UTC
Ping.  We are getting multiple reports of this.
Comment 2 Josh Paetzel 2014-05-23 17:26:59 UTC
https://bugs.freenas.org/issues/5054

Has some core files, logs, and configs.
Comment 3 Volker Lendecke 2014-05-23 17:48:39 UTC
Can you get us a full debug level 10 log of winbind leading to this message?
Comment 4 Craig Schappacher 2014-05-23 18:51:08 UTC
Created attachment 9971 [details]
Syslog of Freenas 9.2.1.6 beta
Comment 5 Volker Lendecke 2014-05-24 08:24:54 UTC
Sorry, but this is not a debug level 10 log of winbind.

Please set

    debug level = 10
     debug pid = true
     max log size = 0

in your smb.conf, restart winbind, reproduce the problem and send all the Samba-related logfiles. Then remove those lines from the smb.conf again and restart winbind again.

Thanks,

Volker
Comment 6 Craig Schappacher 2014-05-27 12:49:29 UTC
Created attachment 9981 [details]
I was able to make changes to the smb4.conf file.
Comment 7 Craig Schappacher 2014-05-27 12:56:45 UTC
I just noticed, when I restart winbindd, the smb4.conf reverts back to original, debug info is gone.
Comment 8 Craig Schappacher 2014-05-27 19:00:58 UTC
Created attachment 9982 [details]
I was able to restart winbindd and generate a new log.
Comment 9 Volker Lendecke 2014-05-27 19:26:15 UTC
This is not a debug level 10 log. Andreas has put together

https://wiki.samba.org/index.php/Bug_Reporting

Please take a look there.

Thanks,

Volker
Comment 10 Craig Schappacher 2014-05-27 20:20:04 UTC
Created attachment 9985 [details]
Error happened @ 4:11
Comment 11 Craig Schappacher 2014-05-27 20:21:37 UTC
Created attachment 9986 [details]
Error happened @ 4:11
Comment 12 Craig Schappacher 2014-05-27 20:22:50 UTC
Created attachment 9987 [details]
Error happened @ 4:11
Comment 13 Volker Lendecke 2014-05-30 09:27:03 UTC
Comment on attachment 9987 [details]
Error happened @ 4:11

Can you please post all logfiles? log.winbindd is not very helpful here, we need all logfiles. winbind writes into more than one log file.
Comment 14 Joerg Altendorf 2014-06-24 11:11:47 UTC
After Upgrading from FreeNAS 9.2.1.5 to 9.2.1.6 RC we also find this error every five minutes in our logs.
We use FreeNAS as Backup-to-Disk media for Backup Exec 2014. This Backup-to-Disk folder is configured as UNC path in Backup Exec. After reading this message https://bugs.freenas.org/issues/5054#note-18 I simply disabled the Backup Exec services for testing purposes for 15 minutes and the error messages are gone. So it looks like to me, that this error is coming from programs, services etc., which are accessing the CIFS share via UNC path. 
I will upload the logs as .zip file
Comment 15 Joerg Altendorf 2014-06-24 11:14:28 UTC
Created attachment 10048 [details]
Attachment to https://bugzilla.samba.org/show_bug.cgi?id=10600#c14