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
Ping. We are getting multiple reports of this.
https://bugs.freenas.org/issues/5054 Has some core files, logs, and configs.
Can you get us a full debug level 10 log of winbind leading to this message?
Created attachment 9971 [details] Syslog of Freenas 9.2.1.6 beta
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
Created attachment 9981 [details] I was able to make changes to the smb4.conf file.
I just noticed, when I restart winbindd, the smb4.conf reverts back to original, debug info is gone.
Created attachment 9982 [details] I was able to restart winbindd and generate a new log.
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
Created attachment 9985 [details] Error happened @ 4:11
Created attachment 9986 [details] Error happened @ 4:11
Created attachment 9987 [details] Error happened @ 4:11
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.
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
Created attachment 10048 [details] Attachment to https://bugzilla.samba.org/show_bug.cgi?id=10600#c14