Project

General

Profile

Bug #4432

sam_sid_to_name: possible deadlock

Added by gear head almost 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Nice to have
Assignee:
Josh Paetzel
Category:
OS
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

I am using FreeNAS-9.2.1.2-RELEASE-x64 (ce022f0). I get the following error message. I don't know the significance of it. Just reporting (in case that it is a bug). Please let me know if you need additional info.

Mar 1 11:01:14 freenas winbindd2158: [2014/03/01 11:01:14.182337, 0] ../source3/winbindd/winbindd_samr.c:694(sam_sid_to_name)
Mar 1 11:01:14 freenas winbindd2158: sam_sid_to_name: possible deadlock - trying to lookup SID S-1-5-21-2618753002-2285421134-873032427-1000


Related issues

Related to FreeNAS - Bug #5054: sam_sid_to_name:possible deadlockResolved2014-05-22

History

#1 Updated by Jordan Hubbard almost 5 years ago

  • Category set to 57
  • Assignee set to John Hixson
  • Target version set to 79

#2 Updated by John Hixson almost 5 years ago

  • Status changed from Unscreened to Screened

#3 Updated by gear head almost 5 years ago

I get this message almost every day. Below is today's which is different from the previously posted one.

Mar 6 11:31:08 freenas kernel: pid 3150 (smbd), uid 1001: exited on signal 11
Mar 6 12:36:06 freenas winbindd2158: [2014/03/06 12:36:06.519523, 0] ../source3/winbindd/winbindd_samr.c:694(sam_sid_to_name)
Mar 6 12:36:06 freenas winbindd2158: sam_sid_to_name: possible deadlock - trying to lookup SID S-1-5-21-3502947525-878643673-3030925372-1001
Mar 6 12:38:41 freenas smbd5897: [2014/03/06 12:38:41.330786, 0] ../source3/modules/vfs_recycle.c:408(recycle_do_touch)
Mar 6 12:38:41 freenas smbd5897: recycle: stat for .recycle/guest/Downloads/7/ADS-2000-inst-H1-USEU.EXE:Zone.Identifier returned No such file or directory
Mar 6 13:04:52 freenas winbindd2158: [2014/03/06 13:04:52.251680, 0] ../source3/winbindd/winbindd_samr.c:694(sam_sid_to_name)
Mar 6 13:04:52 freenas winbindd2158: sam_sid_to_name: possible deadlock - trying to lookup SID S-1-5-21-3502947525-878643673-3030925372-1001
Mar 6 13:04:55 freenas smbd6336: [2014/03/06 13:04:55.279921, 0] ../source3/modules/vfs_recycle.c:408(recycle_do_touch)
Mar 6 13:04:55 freenas smbd6336: recycle: stat for .recycle/guest/Downloads/7/BrMain480.exe:Zone.Identifier returned No such file or directory

#4 Updated by Jordan Hubbard almost 5 years ago

BRB: John - any comment on this one? Should we assign this to Jeremy for comment?

#5 Updated by gear head almost 5 years ago

I am running FreeNAS-9.2.1.3-BETA-e3f3e20-x64. Downloading the latest alpha version version of Freenas to my downloaded folder on server created the error message below:

Mar 16 17:31:18 freenas winbindd2142: [2014/03/16 17:31:18.914599, 0] ../source3/winbindd/winbindd_samr.c:694(sam_sid_to_name)
Mar 16 17:31:18 freenas winbindd2142: sam_sid_to_name: possible deadlock - trying to lookup SID S-1-5-21-2618753002-2285421134-873032427-1000

Perhaps this bit information may help you to duplicate and fix.

#6 Updated by John Hixson almost 5 years ago

  • Status changed from Screened to Investigation

Checking into this.

#7 Updated by John Hixson almost 5 years ago

gear head wrote:

I am running FreeNAS-9.2.1.3-BETA-e3f3e20-x64. Downloading the latest alpha version version of Freenas to my downloaded folder on server created the error message below:

Mar 16 17:31:18 freenas winbindd2142: [2014/03/16 17:31:18.914599, 0] ../source3/winbindd/winbindd_samr.c:694(sam_sid_to_name)
Mar 16 17:31:18 freenas winbindd2142: sam_sid_to_name: possible deadlock - trying to lookup SID S-1-5-21-2618753002-2285421134-873032427-1000

Perhaps this bit information may help you to duplicate and fix.

Can you run this:

wbinfo -s S-1-5-21-2618753002-2285421134-873032427-1000

#8 Updated by gear head almost 5 years ago

Today downloading Freenas 9.2.1.4 to fileserver caused the following message:

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

#9 Updated by gear head almost 5 years ago

John, this issue may have been fixed in Samba 4.1.7:

BUG 10458: Fix 'wbinfo -i' with one-way trust.

#10 Updated by John Hixson almost 5 years ago

gear head wrote:

John, this issue may have been fixed in Samba 4.1.7:

BUG 10458: Fix 'wbinfo -i' with one-way trust.

I'll keep my eyes open. I noticed this as well. Thanks for the heads up.

#11 Updated by gear head almost 5 years ago

John
FreeNAS-9.2.1.6-BETA-e8a3956-x64 produces the same message. So if Samba 4.1.7 has been integrated in it then it is not fixing this issue.

#12 Updated by Josh Paetzel almost 5 years ago

  • Seen in changed from 9.2.1.2-RELEASE to

#13 Updated by Josh Paetzel over 4 years ago

  • Related to Bug #5054: sam_sid_to_name:possible deadlock added

#14 Updated by Josh Paetzel over 4 years ago

The samba team has requested that you turn samba logging to debug and attach the log of the event.

#15 Updated by gear head over 4 years ago

please provide detail instruction on what and how to create the files needed. I have very limited knowledge of this operating system. TIA

#16 Updated by Josh Paetzel over 4 years ago

In service -> CIFS click the wrench to edit the samba settings.
set the log level to debug.

In the extra options add:
debug pid = true

The logfile will be /var/log/messages

#17 Updated by Josh Paetzel over 4 years ago

  • Assignee changed from John Hixson to Josh Paetzel
  • Target version changed from 79 to 95

#18 Updated by Josh Paetzel over 4 years ago

The newest nightly has a new version of samba. Can you test with that please?

#19 Updated by gear head over 4 years ago

Josh, using FreeNAS-9.2.1.6-BETA-3aed4e6-x64, the problem persists. Below is the message:

Jun 6 18:38:14 freenas winbindd2202: STATUS=daemon 'winbindd' finished starting up and ready to serve connectionssam_sid_to_name: possible deadlock - trying to lookup SID S-1-5-21-2618753002-2285421134-873032427-1000
Jun 6 18:38:14 freenas smbd3002: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsnfs4_acls.c: file [Downloads/FreeNas/FreeNAS-10.0.0-ALPHA-99827dc-x64.img.xz.0gp3pa9.partial]: could not convert S-1-5-21-2618753002-2285421134-873032427-1000 to uid or gid
Jun 6 18:39:50 freenas smbd3199: STATUS=daemon 'smbd' finished starting up and ready to serve connectionstrader1-pc (ipv4:192.168.0.1:61316) closed connection to service freenas
Jun 6 18:40:52 freenas winbindd2202: [2014/06/06 18:40:52.968111, 0] ../source3/winbindd/winbindd_samr.c:694(sam_sid_to_name)
Jun 6 18:40:52 freenas winbindd2202: sam_sid_to_name: possible deadlock - trying to lookup SID S-1-5-21-2618753002-2285421134-873032427-1000
Jun 6 18:57:59 freenas smbd3272: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsab02 (ipv4:192.168.0.2:49164) closed connection to service freenas

#20 Updated by gear head over 4 years ago

you said
"In service -> CIFS click the wrench to edit the samba settings.
set the log level to debug.

In the extra options add:
debug pid = true

The logfile will be /var/log/messages""

I don't know how to get to /var/log/messages"", so I can upload the messages. Please provide step by step instruction.

#21 Updated by Josh Paetzel over 4 years ago

The samba team seems to have abandoned us on this, however a usable workaround is to set the max protocol to smb2 in services -> CIFS. Please let me know if you continue to have problems after changing the max protocol setting.

#22 Updated by Josh Paetzel over 4 years ago

  • Target version changed from 95 to 103

#23 Updated by John Hixson over 4 years ago

Can you add the following to your cifs auxiliary parameters and confirm if it gets rid of the message?

idmap config *:backend = tdb
idmap config *:range = 90000000-100000000

#24 Updated by gear head over 4 years ago

Johm I added those two lines to cifs auxiliary parameters. I get the following message:

Jun 24 18:25:00 freenas winbindd22336: STATUS=daemon 'winbindd' finished starting up and ready to serve connectionssam_sid_to_name: possible deadlock - trying to lookup SID S-1-5-21-2618753002-2285421134-873032427-1000
Jun 24 18:25:00 freenas smbd22604: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsnfs4_acls.c: file [Downloads/FreeNas/FreeNAS-9.3-ALPHA-a604b0f-x64.img.xz.eny7snd.partial]: could not convert S-1-5-21-2618753002-2285421134-873032427-1000 to uid or gid

#25 Updated by Josh Paetzel over 4 years ago

Can you attach /usr/local/etc/smb4.conf please?

#26 Updated by Josh Paetzel over 4 years ago

Are you available to do a screen sharing session tomorrow so we can sort this out?

#27 Updated by gear head over 4 years ago

  • File smb4.conf added

Attached is smb4.conf.

#28 Updated by gear head over 4 years ago

Josh, I am going to be very busy the next few days. Then leaving town for a week.

#29 Updated by Chris Dill over 4 years ago

I am experiencing the same issues, and this bug seems to be the root of my inability to join AD. If you would like to get into my box we can set that up.

#30 Updated by Josh Paetzel over 4 years ago

This was reported as fixing this issue in a separate ticket:

[root@freenas] ~# net groupmap list
users (S-1-5-21-3520457182-3639793677-2598286886-1001) -> users
[root@freenas] ~# net groupmap delete sid="S-1-5-21-1170145438-4009580803-3350505473-1001"
Sucessfully removed S-1-5-21-1170145438-4009580803-3350505473-1001 from the mapping db
[root@freenas] ~# net groupmap add unixgroup=users rid=1001
Successfully added group users to the mapping db as a domain group​

#31 Updated by Jordan Hubbard over 4 years ago

  • Target version changed from 103 to 9.3-BETA

#32 Updated by Josh Paetzel over 4 years ago

  • Status changed from Investigation to Resolved
  • Target version changed from 9.3-BETA to 9.2.1.9-RELEASE

This is resolved in the upcoming 9.2.1.9. It's also in the 9.3 nightlies now.

#33 Updated by Marian L over 4 years ago

FreeNAS-9.3-BETA-853426f-x64 - deadlock is still there (https://forums.freenas.org/index.php?threads/deadlock.24653/)

#34 Updated by Dru Lavigne 12 months ago

  • File deleted (smb4.conf)

Also available in: Atom PDF