[Samba] User/Machine RID generation error?
Hello: I'm using: - samba-common-3.0.9-1 - kernel 2.6.5-1.358 - FC 2 - openldap-servers-2.1.29-1 We're running an NT4 domain using an LDAP backend, and everything was running fine until recently. The first thing that I noticed that new users were suddenly being assigned SambaSID's that were previously being assigned to machines. Previously: Typical User Entry: uid: john sambaSID: S-1-5-21-xx-xx-xxx-2416 Typical Machine Entry: uid: somebox$ sambaSID: S-1-5-21-xx-xx-xxx-3134 Now: Typical User Entry: uid: jack sambaSID: S-1-5-21-xx-xx-xxx-3136 So the next time I tried to add the machine newbox, I get this error: -- pdbedit -a -m newbox -d100 --- pdb_set_user_sid: setting user sid S-1-5-21-xx-xx--3136 element 18 - now SET pdb_set_user_sid_from_rid: setting user sid S-1-5-21-xx-xx--3136 from rid 3136 smbldap_search: base = [ou=Groups,dc=somedomain,dc=com], filter = [((objectClass=sambaGroupMapping)(gidNumber=1068))], scope = [2] smbldap_open: already connected to the LDAP server ldapsam_getgroup: Did not find group pdb_set_group_sid: setting group sid S-1-5-21-xx-xx--3137 element 19 - now SET pdb_set_group_sid_from_rid: setting group sid S-1-5-21-xx-xx--3137 from rid 3137 element 20 - now DEFAULT element 33 - now CHANGED element 32 - now CHANGED element 11 - now CHANGED element 21 - now CHANGED account_policy_get: maximum password age:-1 element 10 - now CHANGED account_policy_get: minimum password age:0 element 9 - now CHANGED pdb_set_username: setting username newbox$, was newbox$ element 12 - now CHANGED element 20 - now CHANGED pdb_set_group_sid: setting group sid S-1-5-21-xx-xx--515 element 19 - now CHANGED pdb_set_group_sid_from_rid: setting group sid S-1-5-21-xx-xx--515 from rid 515 smbldap_search: base = [dc=somedomain,dc=com], filter = [(((uid=newbox$)(objectclass=sambaSamAccount))(objectclass=sambaSamAccount))], scope = [2] smbldap_open: already connected to the LDAP server element 18: SET smbldap_search: base = [dc=somedomain,dc=com], filter = [((sambaSID=S-1-5-21-xx-xx--3136)(objectclass=sambaSamAccount))], scope = [2] smbldap_open: already connected to the LDAP server ldapsam_add_sam_account: SID 'S-1-5-21-xx-xx--3136' already in the base, with samba attributes Unable to add machine! (does it already exist?) -- What happened? How does pdbedit generate new RID's? How can I fix this, since as of now I can't add any machines! Please help! Regards, Adnan. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Quickbooks files can't be shared w/ 3.0.11
I had to use the 'veto oplocks' option since I wanted oplocks for everything else on the share. QB works, but nothing else can even read the file. I get a 'Resource Deadlock Avoided' error on smbclient. 'smbstatus' reports a DENY_NONE lock, and an access mode of 0x2019f. I couldn't find the significance of this anywhere. Point to note is that the same setup worked fine without any hitches or errors on Samba 2.2.8. This problem only surfaced when I upgraded to 3.0.11. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Randy S Sent: Thursday, March 03, 2005 3:01 PM To: Mitch (WebCob) Cc: samba@lists.samba.org Subject: Re: [Samba] Quickbooks files can't be shared w/ 3.0.11 I had to add these to the share to get that working properly. I've probably added some stuff that's not needed, but it worked, so I left it. I think the oplocks setting is key though. create mask = 0777 force create mode = 0777 oplocks = no force directory security mode = 0777 Mitch (WebCob) wrote: The second instance of Quickbooks shows a file may be corrupt message. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Resource deadlock avoided
Hello: I also have the same problem on files that, according to smbstatus, have: DenyMode: DENY_NONE Oplocks:NONE Strangely enough this is only happening for one Mac user. And even then this only happens for two of the 20+ files he's got open, and the only apparent difference between them is in the Access column: the offending files have Access: 0x3. If I use 'smbstatus -L', it lists files open on this user's computer, yet reports *no* locks when I use 'smbstatus -u username -L'. An smbstatus bug, perhaps? Also, the '[Errno 35] Resource Deadlock Avoided' messages only started showing up after I upgraded the fileserver to: OS: Fedora Core 3 Kernel: 2.6.9-1.667 Samba: 3.0.11-1 What could be causing this problem? Any help would be greatly appreciated. Thanks! Regards, Adnan. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of David Wilson Sent: Monday, February 21, 2005 9:41 AM To: samba@lists.samba.org Subject: [Samba] Resource deadlock avoided Hi guys, How are you keeping ? I use 'smbmount' and a custom script to mount remote shares from Windows desktops and back them up to a Linux server. Everything works great except that I get Resource deadlock avoided when trying to copy 'Outlook.pst'. This of course is due to users' having their Outlook open when my backup script runs. Is anyone aware of a way to avoid the 'Resource deadlock avoided error and still copy 'Outlook.pst' file ? I've had a look around but can't find too much info on this. Thanks in advance. Kindest regards David Wilson ___ D c D a t a Tel +27 33 342 7003 Fax +27 33 345 4155 Cell +27 82 4147413 http://www.dcdata.co.za [EMAIL PROTECTED] Powered by Linux, driven by passion ! ___ Computers are not intelligent. They only think they are. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
