[Samba] `samba-tool dbcheck --cross-ncs --fix` fails: governsID already exists as an attributeId or governsId
rpenny at samba.org
Thu Jul 4 13:54:22 UTC 2019
On 04/07/2019 14:45, Sven Schwedas via samba wrote:
> On 03.07.19 18:04, Rowland penny via samba wrote:
>>>>> How do I get rid of these bogus Schema entries, and how do I fix the
>>>>> user account?
>>>> I do not think you can remove anything from the schema, but I believe
>>>> you can deactivate schema objects, try reading this:
>>> They already are disabled.
>> Have you extended the schema to use 'taouser' ?
>> I ask this because (from what you posted) it uses the same X500 OID as
>> 'ucsUser', another name for X500 OID is 'governsID', so this may be your
>> problem, try deleting 'taouser' from your AD object (this is allowed)
>> and see if your problem goes away.
> That fixed the dbcheck crashes on the other three servers, they now
> complete successfully.
> Still left are the three governsId collisions, which are now identical
> across all DCs:
>> Checking 3861 objects
>> Error: governsID CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on 22.214.171.124.4.1.194126.96.36.199 already exists as an attributeId or governsId
>> Error: governsID CN=taoSharedFolder,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on 188.8.131.52.4.1.194184.108.40.206 already exists as an attributeId or governsId
>> Error: governsID CN=taoMailingList,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on 220.127.116.11.4.1.19418.104.22.168 already exists as an attributeId or governsId
>> Checked 3861 objects (3 errors)
> How do I fix those? Can I just edit the old, defunct classes and change
> their governsId without breaking something?
I do not know, mainly because I have never tried to do something like
this on a production server.
More information about the samba