sam_rids_to_names: possible deadlock - trying to lookup SID

[lpittman]

I have been experiencing this issue as well and thought I would just try disabling winbindd. To do this I edited /etc/local/rc.d/samba_server, searched for winbindd and just changed a couple of things:

Code:

#samba_daemons="nmbd smbd winbindd"
samba_daemons="nmbd smbd"

and

Code:

#winbindd_enable="YES"
winbindd_enable="NO"

Then I restarted the service, no more error and no more permission problems.

I know this isn't a fix, but it did get me back online.

 

[Knowltey]

I have been experiencing this issue as well and thought I would just try disabling winbindd. To do this I edited /etc/local/rc.d/samba_server, searched for winbindd and just changed a couple of things:

Code:

#samba_daemons="nmbd smbd winbindd"
samba_daemons="nmbd smbd"

and

Code:

#winbindd_enable="YES"
winbindd_enable="NO"

Then I restarted the service, no more error and no more permission problems.

I know this isn't a fix, but it did get me back online.

I wouldn't advise that, windbindd is sort of needed to make your permissions work properly and the errors itself was harmless, just spammy.

 

[lpittman]

I wouldn't advise that, windbindd is sort of needed to make your permissions work properly and the errors itself was harmless, just spammy.

I figured I might be opening myself up for other issues, however I thought I'd try it out. I only use guest access so it hasn't affected me yet.

The issue is for me it wasn't just spammy - I was completely unable to access anything when this error appeared, just got access denied errors in Windows. Everything I tried would not fix my access issues, so I tried this.

Any ideas on what the main issue might be for me then?

 

[Knowltey]

I figured I might be opening myself up for other issues, however I thought I'd try it out. I only use guest access so it hasn't affected me yet.

The issue is for me it wasn't just spammy - I was completely unable to access anything when this error appeared, just got access denied errors in Windows. Everything I tried would not fix my access issues, so I tried this.

Any ideas on what the main issue might be for me then?

It's a currently known issue with the current release. It's related to the net groupmap list and it not being populated correctly after reboots.

Do your ACLs reflect the guest only access, or do you have group ACLs on your shares as well? winbindd manages the name resolution for group names to SID, so that is where the error comes up. (They still work despite the error, the issue the error will cause is an inability to edit them by name) (Basically it'd be like having to access google.com via 74.125.224.34 instead of via google.com, but for security groups instead of websites)

If you go to my post earlier in the thread (http://forums.freenas.org/index.php...trying-to-lookup-sid.21982/page-3#post-135950) I have outlined the workaround I used as well as quoted the original person who found the workaround. His used a bit of the "long way around" so to speak by deleting each groupmap on a one by one basis, whereas I just used the net groupmap cleanup command and manually readded all of them.

 

[Ismael Duarte]

Something new.
When I type "net groupmap list" , the 1st line shows
"Environment LOGNAME is not defined. Trying anonymous access."
What does it mean?

 

[Eric10301]

This bug is driving me nuts. I'm one of the unlucky ones who has their connection drop once it hits. I tried the "fix" a couple pages back and it didn't work for me.

 

[Knowltey]

This bug is driving me nuts. I'm one of the unlucky ones who has their connection drop once it hits. I tried the "fix" a couple pages back and it didn't work for me.

You'll want to open another thread for troubleshooting since you seem to have something secondary going on as well. All other cases of this have it just being spammy but not service effecting.

 

[diedrichg]

edit: nevermind, still showing errors in 9.2.1.8

 

[anodos]

https://bugs.freenas.org/issues/6192

I believe this will be fixed in 9.2.1.9

 

[Ericloewe]

https://bugs.freenas.org/issues/6192

I believe this will be fixed in 9.2.1.9

9.2.1.9? I'm not one to complain about improvements, but what popped up so soon after 9.2.1.8?

 

[anodos]

9.2.1.9? I'm not one to complain about improvements, but what popped up so soon after 9.2.1.8?

Best guess is that it is because samba4 was missing a dependency causing its internal DNS to break thereby preventing it from acting as an ad DC. Oops :)

 

[Ericloewe]

Best guess is that it is because samba4 was missing a dependency causing its internal DNS to break thereby preventing it from acting as an ad DC. Oops :)

Are there so few daredevils running Samba as a domain controller that it took so long to figure out something was amiss?

 

[rhdd]

Maybe the others are using BIND instead of samba internal DNS.

 

[anodos]

Maybe the others are using BIND instead of samba internal DNS.

Problem was introduced in 9.2.1.8 see bug report here: https://bugs.freenas.org/issues/6241

 

[Andy Li]

FYI, this issue has been fixed in 9.2.1.9. I upgraded to 9.2.1.9. The deadlock errors no longer exists even after a reboot.

 

[indy]

I upgraded to 9.2.1.9 and the deadlock error still persists.

Aditionally I am now getting this error

Code:

freenas smbd[44541]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsWARNING: The "acl check permissions" option is deprecated

Might be unrelated though.

 

[anodos]

I upgraded to 9.2.1.9 and the deadlock error still persists.

Aditionally I am now getting this error

Code:

freenas smbd[44541]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsWARNING: The "acl check permissions" option is deprecated

Might be unrelated though.

That's a totally benign error message. I think the freenas CIFS guy even commented out the code generating the message in 9.3.

I asked once about the parameter on the samba mailing list and was met with crickets. :)

 

[indy]

That is good to know.
Just a bit unfortunate that the console gets 'spammed' with these messages.

 

[anodos]

Just an update. Josh posted instructions on using a python script he wrote to fix this problem. See here: https://forums.freenas.org/index.php?threads/plagued-by-name-to-sid-deadlock-errors.25204/

 

[GrahamBB]

Still seeing the problem on the latest (9.3 08/23) build.