search for: nextrid

...6: Failed to re-index objectSid in CN=test > user,CN=Users,DC=chester-dc,DC=example,DC=com - > ../ldb_tdb/ldb_index.c:1148: unique index violation on objectSid in > CN=test user,CN=Users,DC=chester-dc,DC=example,DC=com G'Day, This is a serious situation. What it means is that the nextRid value for that DC points at a user account that already exists, so when we go to create it, the create fails. That, and the other issue, suggests you have had some serious DB corruption, and this may not be the only issues. Does a full dbcheck pass? (Not just the reindex). Is there another DC th...

...nLDAP backend smbldap-tools and I have a problem with RID allocation. Long time ago (before Samba 3.0.25?) RID was generated this way: uid * 2 + 1000 gid * 2 + 1001 and it was nice and predictable. Now, as far as I'm aware of, Samba with LDAP backend don't do that any more. It uses sambaNextRid attribute. I was trying to use smbldap-tools to generate the sambaSAMaccount but I was getting those nasty errors like the need of adding machine to domain twice and so on... ("A device attached to the system is not functioning" - error). I guess it's because Samba was trying to c...

...7,CN=Servers,CN=Default-First-Site >>> -Name,CN=Sites,CN=Configuration,DC=micore,DC=us >>> ... >>> >>>>> Try running this on the DC: ldbsearch >>>>> -H/usr/local/samba/private/sa m.ldb '(objectClass=rIDSet)' dn >>>>> rIDNextRID >>>> It should should show the DN's of your DCs followed by the contents >>>> of the 'rIDNextRID' attributes. these should be '0' on all DC's >>>> except the RID master. >>> >>> [root at larkin28 ~]# ldbsearch -H /var/lib...

On 17/05/16 12:11, ash-samba at comtek.co.uk wrote: > >> G'Day, >> >> This is a serious situation. What it means is that the nextRid value >> for that DC points at a user account that already exists, so when we >> go to create it, the create fails. > I've just looked at the LDAP output, and nextRid is 1000 for both dn: > CN=Builtin,DC=chester-dc,etc and for dn: DC=chester-dc,etc Same here. > > Th...

...> Settings,CN=LARKIN27,CN=Servers,CN=Default-First-Site >> -Name,CN=Sites,CN=Configuration,DC=micore,DC=us >> ... >> >>>> Try running this on the DC: ldbsearch >>>> -H/usr/local/samba/private/sa m.ldb '(objectClass=rIDSet)' dn >>>> rIDNextRID >>> It should should show the DN's of your DCs followed by the contents >>> of the 'rIDNextRID' attributes. these should be '0' on all DC's >>> except the RID master. >> >> [root at larkin28 ~]# ldbsearch -H /var/lib/samba/private/sam.l...

> G'Day, > > This is a serious situation. What it means is that the nextRid value for that DC points at a user account that already exists, so when we go to create it, the create fails. I've just looked at the LDAP output, and nextRid is 1000 for both dn: CN=Builtin,DC=chester-dc,etc and for dn: DC=chester-dc,etc The most recent successful new user (that I'm awar...

...Site > >>> -Name,CN=Sites,CN=Configuration,DC=micore,DC=us > >>> ... > >>> > >>>>> Try running this on the DC: ldbsearch > >>>>> -H/usr/local/samba/private/sa m.ldb '(objectClass=rIDSet)' dn > >>>>> rIDNextRID > >>>> It should should show the DN's of your DCs followed by the > >>>> contents of the 'rIDNextRID' attributes. these should be '0' on > >>>> all DC's except the RID master. > >>> > >>> [root at larkin28...

...e owner: CN=NTDS > Settings,CN=LARKIN27,CN=Servers,CN=Default-First-Site > -Name,CN=Sites,CN=Configuration,DC=micore,DC=us > ... > > > > Try running this on the DC: ldbsearch > > > -H/usr/local/samba/private/sa m.ldb '(objectClass=rIDSet)' dn > > > rIDNextRID > > It should should show the DN's of your DCs followed by the contents > > of the 'rIDNextRID' attributes. these should be '0' on all DC's > > except the RID master. > > > [root at larkin28 ~]# ldbsearch -H /var/lib/samba/private/sam.ldb >...

...gt;> -Name,CN=Sites,CN=Configuration,DC=micore,DC=us >>>>> ... >>>>> >>>>>>> Try running this on the DC: ldbsearch >>>>>>> -H/usr/local/samba/private/sa m.ldb '(objectClass=rIDSet)' dn >>>>>>> rIDNextRID >>>>>> It should should show the DN's of your DCs followed by the >>>>>> contents of the 'rIDNextRID' attributes. these should be '0' on >>>>>> all DC's except the RID master. >>>>> [root at larkin28 ~]# ld...

...ne located on another continent, with a quite unreliable link!), >> and that gives us an account with >> S-1-5-21-2702589905-558746101-3641499263-7125 on -both- alaska and >> empire, so there is clearly some amount of working replication. >> Confusingly, after doing this nextRid is still 1000 on both machines. > > This could be because you are looking at the wrong attribute in the > wrong place. > Try looking at the object 'CN=RID Set,CN=ALASKA,OU=Domain > Controllers,DC=CHESTER-DC,DC=EXAMPLE,DC=COM' and the attribute > 'rIDNextRID' it...

On Sun, 2020-08-30 at 02:57 -0700, Peter Pollock wrote: > Yeah, I already tried that, to no avail. What exactly was the error or symptom? Did you try the backup and restore I suggested? If the only issue is the RID, there are ways to get past that - changing the nextRid for example, but you might wish to engage professional Samba support. I get the impression you are pretty stressed. One of the things I've seen with stressed administrators over the years is big jumps without careful notes. Take each step slowly, get good advise (here or professionally) and...

...n ldapsam_get_new_rid (priv=0x80027aa8, rid=0xbffffb58) at ../source3/passdb/pdb_ldap.c:4854 smbldap_state = 0x80027fc0 result = 0x80036740 entry = 0x80036740 mods = 0x80011a98 status = {v = 0} value = 0x0 rc = -2147280760 nextRid = 1012 dn = 0xb70dbd06 "LDAPMessage *" mem_ctx = 0x80032f78 __FUNCTION__ = "ldapsam_get_new_rid" #2 0xb7d45c33 in ldapsam_new_rid_internal (methods=0x80027e28, rid=0xbffffb58) at ../source3/passdb/pdb_ldap.c:4882 result = {v = 0}...

Yeah, I already tried that, to no avail. I finally had some modicum of success. Switched everything off except one server, then restored that from June and was able to then build a new server and join it to the domain. And everything was peachy. Except the original server has some stupid zentyal issues which no one on the zentyal boards can help me fix and when I then demoted the original

> This certainly sounds stressful. Yes! > Another way to (on a backup, particularly given your history above) remove the index is with samba-tool dbcheck --reindex. Re-indexing... completed re-index OK 0 root at empire:~[0] samba-tool dns add empire chester-dc.example.com p-cats A 10.4.4.142 -U ash Password for [CHESTER-DC\ash]: Record added successfully Thanks! > The missing

On Fri, Mar 04, 2016 at 04:16:44PM +0000, Rowland penny wrote: > On 04/03/16 09:58, Volker Lendecke wrote: > >On Fri, Mar 04, 2016 at 10:53:17AM +0100, Volker Lendecke wrote: > >>On Wed, Mar 02, 2016 at 09:23:34AM +0000, Rowland penny wrote: > >>>OK, here is the output: > >>Can you try the attached (UNTESTED!) patch? > >> > >>Thanks, >