Plagued by name to sid deadlock errors?

Status
Not open for further replies.
J

jpaetzel

Guest
I added a tool to 9.3 this weekend that will help resolve most cases of this. By popular request I backported it to 9.2.1.9. If you're running an older version of 9.2.1.x you'll have to update to 9.2.1.9 before running the tool.

Code:
mountrw /
fetch "http://download.freenas.org/errata/fixsid.py" -o /usr/local/bin/fixsid.py
chmod 755 /usr/local/bin/fixsid.py
mount -ur /
rehash
fixsid.py
 

diedrichg

Wizard
Joined
Dec 4, 2012
Messages
1,319
I keep getting
Code:
[root@freenas /usr/local/bin]# fetch "http://download.freenas.org/errata/fixsid.
py" -o /usr/local/bin/fixsid.py                                                
fixsid.py                                     100% of 2312  B   36 MBps 00m00s 
fetch: -o: No such file or directory                                           
fixsid.py                                     100% of 2312  B  146 MBps 00m00s  
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
I think there was a typo in the first post, it should be 'mount -rw /'
 

diedrichg

Wizard
Joined
Dec 4, 2012
Messages
1,319
Oh! Yup! I see that now, duh!
 

rlambie

Cadet
Joined
Dec 3, 2014
Messages
1
I keep getting the following message:

Code:
[root@DENHAM] ~# fixsid.py
Multiple SIDs detected, aborting without making changes.
 

diedrichg

Wizard
Joined
Dec 4, 2012
Messages
1,319
I'm still getting the error in post #2.
 

ashori

Dabbler
Joined
Jun 17, 2014
Messages
17
Hi all, am getting similar errors:

[root@Medusa ~]# mount -rw /
[root@Medusa ~]# fetch "http://download.freenas.org/errata/fixsid.py" -o /usr/local/bin/fixsid.py
fixsid.py 100% of 2312 B 21 MBps 00m00s
fetch: -o: No such file or directory
fetch: /usr/local/bin/fixsid.py: No such file or directory
[root@Medusa ~]# chmod 755 /usr/local/bin/fixsid.py
chmod: /usr/local/bin/fixsid.py: No such file or directory
[root@Medusa ~]#

Any suggestions please?
 

toadman

Guru
Joined
Jun 4, 2013
Messages
619
If the wget completes the file is in / (or wherever you were when you executed the wget). So just move the file to /usr/local/bin/fixsid.py. i.e. do:
Code:
mv ./fixsid.py /usr/local/bin/fixsid.py


Then do the chmod on that file as indicated.

BTW the path didn't update for me, so I just did a cd into /usr/local/bin and executed ./fixsid.py
 

ashori

Dabbler
Joined
Jun 17, 2014
Messages
17
Did the above, seems to have worked. Haven't seen any more error messages in the console.

I noticed the rehash command didn't work during the fix though..

<edit>
Whoops looks like it didnt work after all... maybe the rehash was an important step :0?
Dec 9 15:00:26 Medusa nmbd[28985]: STATUS=daemon 'nmbd' finished starting up and ready to serve connections*****
Dec 9 15:00:26 Medusa nmbd[28985]:
Dec 9 15:00:26 Medusa nmbd[28985]: Samba name server MEDUSA is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.30
Dec 9 15:00:26 Medusa nmbd[28985]:
Dec 9 15:00:26 Medusa nmbd[28985]: *****
Dec 9 15:16:14 Medusa smbd[29902]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 192.168.1.8 != (NULL)
Dec 9 15:16:14 Medusa smbd[29902]: [2014/12/09 15:16:14.293734, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Dec 9 15:16:14 Medusa smbd[29902]: matchname failed on 192.168.1.8

<edit #2>
Hmm, this might be a different issue, after scrolling up the log I see the original error is different.

Dec 6 16:55:35 Medusa winbindd[17354]: [2014/12/06 16:55:35.987717, 0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Dec 6 16:55:36 Medusa winbindd[17354]: sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-3881774620-4133175558-3297749440
 
Last edited:

diedrichg

Wizard
Joined
Dec 4, 2012
Messages
1,319
can't get rehash to work either
 

hervon

Patron
Joined
Apr 23, 2012
Messages
353
I keep getting the following message:

Code:
[root@DENHAM] ~# fixsid.py
Multiple SIDs detected, aborting without making changes.

Same thing for me with 9.3 Stable. Any way to correct this issue ?
 

Josh Johnson

Cadet
Joined
Oct 5, 2013
Messages
2
I have 9.3 Stable and I fixed mine with the following changes
-My / was already mounted so no need for 1
-I did 4 but then when i ran script i got trying to write to read only database errors
-'rehash' command didnt exist for me so i googled that hash -r is a replacement and it ran

Original
  1. mountrw /
  2. fetch "http://download.freenas.org/errata/fixsid.py" -o /usr/local/bin/fixsid.py
  3. chmod 755 /usr/local/bin/fixsid.py
  4. mount -ur /
  5. rehash
  6. fixsid.py
Mine
  1. fetch "http://download.freenas.org/errata/fixsid.py" -o /usr/local/bin/fixsid.py
  2. chmod 755 /usr/local/bin/fixsid.py
  3. mount -urw /
  4. hash -r
  5. fixsid.py
  6. Run the commands the script says to after completion or reboot
I havent gotten another sid error in the last ten minutes since running
 

diedrichg

Wizard
Joined
Dec 4, 2012
Messages
1,319
Thank you. I'll give this a go later.
 

escalibur

Dabbler
Joined
Jan 3, 2015
Messages
49
I'm also having deadlock errors (FreeNAS-9.3-STABLE-201501090144) so could this fix be included officially?

winbindd[2450]: sam_rids_to_names: possible deadlock - trying to lookup SID....
 

Josh Johnson

Cadet
Joined
Oct 5, 2013
Messages
2
Like they say every where else the sid deadlock errors could be multiple things, they can't include a fix for it. Take snapshots and try the different fixes until one works for you.
 

SkyMonkey

Contributor
Joined
Mar 13, 2013
Messages
102
On my system (9.3 stable), I'm still getting this message. Specifically, I get it when trying to add certain users/groups to files and directories through the windows security dialog on datashares shared out via CIFS with windows permissions. The error occurs when I attempt to add users/groups that exist in freenas, but they fail to be found in the windows dialog and this error appears in the console.

I am going to attempt the instructions above and see if this fixes the issue.

---------

Edit: Script did not run:

"Multiple SIDs detected, aborting without making changes."

Unfortunately, I cannot seem to add certain users/groups to files/directories in windows using window security dialog at this point. Some recently created groups work just fine, but other, older groups are not found by windows and cause this error in the console.

Code:
Jan 17 17:48:51 freenas winbindd[2606]: sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-626537768-3214805501-4061107804
Jan 17 17:48:51 freenas winbindd[2606]: [2015/01/17 17:48:51.712227, 0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Jan 17 17:48:51 freenas winbindd[2606]: sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-626537768-3214805501-4061107804
Jan 17 17:49:06 freenas smbd[26746]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsreceive_smb_raw_talloc failed for client ipv4:192.168.42.69:54727 read error = NT_STATUS_CONNECTION_RESET.
Jan 17 17:49:10 freenas winbindd[2606]: [2015/01/17 17:49:10.616896, 0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Jan 17 17:49:10 freenas winbindd[2606]: sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-626537768-3214805501-4061107804
Jan 17 17:49:24 freenas smbd[26801]: STATUS=daemon 'smbd' finished starting up and ready to serve


Occasionally I also get:
Code:
Jan 17 17:44:42 freenas smbd[26460]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionscreate_connection_session_info failed: NT_STATUS_ACCESS_DENIED
 
Last edited:
Status
Not open for further replies.
Top