[Samba] Samba 4.5.0 dbcheck problems

lingpanda101 at gmail.com lingpanda101 at gmail.com
Wed Oct 12 13:23:16 UTC 2016


On 10/12/2016 8:29 AM, Chris Alavoine via samba wrote:
> Hi all,
>
> I've recently upgraded all our DC's (we have 9 spread over various global
> Sites) to 4.5.0.
>
> I run a dbcheck on our FSMO-owner DC once per day from a cron job and this
> threw up a ton of errors on the first pass after the upgrade. After running
> it several times with the --fix flag I've got the errors down to 603 but
> these last errors are refusing to be removed.
>
> Here is an example of each type:
>
> Example1:
> *ERROR: incorrect GUID component for member in object
> CN=examplegroup,OU=Groups,DC=example,DC=internal,DC=com -
> <GUID=77ad92b5ade70e449dcc481624928310>;<RMD_ADDTIME=130393476680000000>;<RMD_CHANGETIME=130976799640000000>;<RMD_FLAGS=1>;<RMD_INVOCID=98307faefea70749933e6946b1b14420>;<RMD_LOCAL_USN=1445979>;<RMD_ORIGINATING_USN=303848>;<RMD_VERSION=1>;<SID=010500000000000515000000e8e83f391df4408a63c6a6b4d25a0000>;CN=simon.test,CN=Users,DC=example,DC=internal,DC=com*
>
> Example2:
> *ERROR: incorrect DN string component for member in object
> CN=admin-group-001,OU=Groups,DC=example,DC=internal,DC=com -
> <GUID=38370cfc-6751-49bb-945e-d2b5e028f0f3>;<RMD_ADDTIME=130941544260000000>;<RMD_CHANGETIME=130941560040000000>;<RMD_FLAGS=1>;<RMD_INVOCID=a65d0f39-311e-4031-aa56-a8585bfc1b8f>;<RMD_LOCAL_USN=1443123>;<RMD_ORIGINATING_USN=1443123>;<RMD_VERSION=1>;<SID=S-1-5-21-960489704-2319512605-3030828643-1219569>;CN=user.test,OU=Test
> OU,DC=example,DC=internal,DC=com*
>
> Example3:
> *unable to find object for DN
> CN=test.user2,CN=Users,DC=example,DC=internal,DC=com - (No such Base DN:
> CN=test.user2,CN=Users,DC=example,DC=internal,DC=com)*
> *Not removing dangling forward link*
>
> I have edited these entries to maintain anonymity.
>
> Any ideas on how to remove these errors?
>
> Replication appears to be working fine between all DCs (aside from one that
> is showing a WERR_BADFILE error, although I don't think this is related),
> we are able to use the domain as normal and performance seems good. Would
> be nice to clean up these errors though.
>
> Thanks,
> Chris.
>
>

I had similar issues. The GUID errors should be harmless. See my thread 
for reference.

http://samba.2283325.n4.nabble.com/replPropertyMetaData-amp-KCC-issues-after-updating-to-Samba-4-5-0-td4707962.html#a4708208

-- 
-James




More information about the samba mailing list