WINBINDD possible deadlock :(

Status
Not open for further replies.

Goned

Explorer
Joined
Jan 26, 2015
Messages
78
Hi,

I have this error = STATUS=daemon 'winbindd' finished starting up and ready to serve connectionssam_rids_to_names: possible deadlock - trying to lookup

What is this ???? If i look the security of sharing, i see unknow account....

:(
 

BigDave

FreeNAS Enthusiast
Joined
Oct 6, 2013
Messages
2,479

Fuzzy_Dunlop

Cadet
Joined
Aug 13, 2013
Messages
6
It's caused by the most recent update for the stable branch of FreeNAS 9.3. My log now constantly displays these errors whenever I access a cifs share. I tried rolling back to the previous update but for whatever reason that made some of my shares inaccessible, so I reluctantly reverted back to the newest version.

What's frustrating is a previous update (9.2.1.5 or 9.2.1.6 I believe) caused this same thing to happen and it took months before it was finally fixed. Hopefully this time it gets fixed sooner.
 

Goned

Explorer
Joined
Jan 26, 2015
Messages
78
Yes, i access too a cifs share. But is very new for me this displays errors....maybe resolved with the next update....
 

JJT211

Patron
Joined
Jul 4, 2014
Messages
323
nm
 

Ismael Duarte

Contributor
Joined
Jun 13, 2011
Messages
154
Well, there's a lot of it, yes. But still an error on most updated versions.
I've seen a lot of posts and after all this posts still don't know how to fix it.

The error is:
Code:
possible deadlock - trying to lookup SID S-1-5-21-1968532309-4128643968-1896509256


net groupmap list
Code:
Familia (S-1-5-21-126775506-3417158065-3122785809-1003) -> Familia
dispositivos (S-1-5-21-126775506-3417158065-3122785809-1002) -> dispositivos
Controlo (S-1-5-21-1968532309-4128643968-1896509256-1001) -> Controlo


Then I do a net groupmap cleanup
followed by opening a group and OK, the groupmap is recreated and is now like this
Code:
dispositivos (S-1-5-21-126775506-3417158065-3122785809-1003) -> dispositivos
Familia (S-1-5-21-1865571458-1680185543-2058147840-1001) -> Familia
Controlo (S-1-5-21-126775506-3417158065-3122785809-1002) -> Controlo


Everything changed

Seems to solve the issue until next reboot.
 
Status
Not open for further replies.
Top