similar to: samba getting stuck, highwatermark replication issue?

Hi James, Thanks for the quick reply. On 10/09/2017 08:52 PM, lingpanda101 via samba wrote: > You should be able to fix the 'replPropertyMetaData' errors with; > > samba-tool dbcheck --cross-ncs --fix --yes > 'fix_replmetadata_unsorted_attid' Yep, worked great! Fixed all of those replPropertyMetaData errors! :-) > The highwatermark doesn't necessarily

On 10/9/2017 1:28 PM, mj via samba wrote: > Hi all, > > We would appreciate some input here. Not sure where to look... > > We have three AD DCs, all running samba 4.5.10, and since a few days, > the samba DCs are getting stuck regularly, at ramdon times. Happens to > all three of them, randomly, and currently it is happening up to a few > times per day..! Must be some

On 10/17/2017 11:22 AM, Andrew Bartlett wrote: > > Can you please be less vague on what the link is exactly? A suggestion > around the office from Garming was that we should: Oh sure! I posted that info already, I think, but this is the error: > ERROR: no target object found for GUID component for msDS-NC-Replica-Locations in object

On 10/16/2017 08:56 PM, Andrew Bartlett wrote: > Are they breaking anything? Not sure. But in another thread I reported some issues on replication, highwatermark notifications, high COU load, etc. My idea was do try several things to fix this. SO I created a virtualised isolated environment, in which I can try out all kinds of things: - upgrading the DCs to 4.7 (as suggested by you) or -

On 17/11/2020 11:54, mj via samba wrote: > Hi, > > Checking a bit more today, as the two changes on DC4 have *still* not > propagated? to DC2/DC3, I discovered the > ?samba-tool drs uptodateness > command. > > I gives the following output, not sure what "unknown invocation ID" > means. I hope someone here is able to explain..? > > It's output: >

Hi all, We are running a three DC samba AD, using 4.12.8 sernet packages. Very stable for years. Today at 12:30 my colleague moved two users from * CN=Users,DC=samba,DC=company,DC=com to * OU=disabled,DC=samba,DC=company,DC=com This change was done on the DC4 at 12:30 using LAM (ldap-account-manager version 7.3) Ever since that, my automated samba-tool ldapcmp scripts started reporting

On 10/16/2017 11:13 AM, Rowland Penny via samba wrote: > On Mon, 16 Oct 2017 16:53:17 +0200 > mj via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> dbcheck tells us we have two "dangling forward links" that I am >> trying to get rid of. On my test domain, I have simply done >> >> ldbedit -e nano -H

On 10/10/2017 3:14 AM, mj via samba wrote: > Hi James, > > Thanks for the quick reply. > > On 10/09/2017 08:52 PM, lingpanda101 via samba wrote: > >> You should be able to fix the 'replPropertyMetaData' errors with; >> >> samba-tool dbcheck --cross-ncs --fix --yes >> 'fix_replmetadata_unsorted_attid' > Yep, worked great! Fixed all of

hello our AD domain is hosted by two samba AD domain controllers version 4.12.6 - replication between controllers is fine, no problems. - no schema errors. - no database errors, all fine. - no CPU utilizations - wthout noticeable bandwidth utilization Recently we have deployed Azure AD connector on dedicated windows system (system is domain member server). since this deployment we are observing

Hi all, James, After following James' suggestions fixing the several dbcheck errors, and having observed things for a few days, I'd like to update this issue, and hope for some new input again. :-) Summary: three DCs, all three running Version 4.5.10-SerNet-Debian-16.wheezy, samba-tool dbcheck --cross-ncs reports no errors, except for two (supposedly innocent) dangling forward links

Hi Michal, Seems we are doing similar things at the moment: getting samba to work with azure AD. We also see the high CPU usage on the DC that the Azure AD Connect server connected to. Between 70 - 100 percent in our case. We are not seeing any replication issues after azure AD Connect, and I have a script that automatically checks replication every few minutes. I was the one reporting the

On Tue, 2017-10-17 at 11:42 +0200, mj wrote: > > On 10/17/2017 11:22 AM, Andrew Bartlett wrote: > > > > Can you please be less vague on what the link is exactly? A suggestion > > around the office from Garming was that we should: > > Oh sure! I posted that info already, I think, but this is the error: > > > ERROR: no target object found for GUID

just small update: - idfix tool (Directory Synchronization Error Remediation Tool / https://github.com/microsoft/idfix) shows just small issues like empty/missing displayName attrib in some of objects which I have corrected and no more issues present at all. - no errors from AAD connect event viewer: final log message is "Scheduler::SchedulerThreadMain : Completed configured scheduler

Hi, Checking a bit more today, as the two changes on DC4 have *still* not propagated to DC2/DC3, I discovered the samba-tool drs uptodateness command. I gives the following output, not sure what "unknown invocation ID" means. I hope someone here is able to explain..? It's output: > root at dc2:~# samba-tool drs uptodateness > Unknown invocation ID

Same as MJ and You. So you have 5 DC's running. > >>> Unknown invocation ID 556b2cb4-e576-48e2-bb7c-7f62caee84fc > >>> Unknown invocation ID 7281ff0f-5af2-4ded-bdaf-362f1545d221 > >>> Unknown invocation ID 82b24c02-16cb-4ed1-b68b-a047c26886a9 > >>> Unknown invocation ID b97cc603-6d03-4ad0-8629-be408fed8d69 > >>> Unknown invocation

Hi all, We seem to have some issues with our samba4 ad setup. I posted about this last week already but had received no replies at all so far. :-( What is our situation: two domain controllers (dc1 and dc2), one (separate) fileserver, all running sernet-4.1.7. From the workstations perspective, everything is running as it should, there appear to be no issues. However: something in my

Hi all, Samba (sernet) 4.1.7, and we're getting high cpu usage on dc1, and on dc2 (my 'secondary' dc): root at dc2:~# samba-tool drs showrepl Default-First-Site-Name\DC2 DSA Options: 0x00000001 DSA object GUID: 5e93a102-2963-496a-af16-0c51eebb2e31 DSA invocationId: 82b24c02-16cb-4ed1-b68b-a047c26886a9 ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=samba,DC=domain,DC=com

On 10/12/2017 3:17 AM, mj wrote: > Hi all, James, > > After following James' suggestions fixing the several dbcheck errors, > and having observed things for a few days, I'd like to update this > issue, and hope for some new input again. :-) > > Summary: three DCs, all three running Version > 4.5.10-SerNet-Debian-16.wheezy, samba-tool dbcheck --cross-ncs reports

I am attempting to add a Windows 2008R2 DC to my S4 domain... and it always stalls out attempting to replicate CN=Configuration object X of Y. So I have been digging, digging, digging, and I found this in the log file of the DC the 2008R2 box is attempting to replicate from - Feb 1 16:52:42 larkin28 samba[18650]: ../source4/rpc_server/drsuapi/getncchanges.c:1961: DsGetNCChanges 2nd

Hello, I upgrade the schema for our main ADDC and everything works properly, but the member DC (DC to an Existing AD) fails. Both servers are in version 4.10.2 Distro: Debian 9.8 *Main ADDC:* [2019/04/16 15:43:03.814846, 0] ../../source4/rpc_server/drsuapi/getncchanges.c:2919(dcesrv_drsuapi_DsGetNCChanges) ../../source4/rpc_server/drsuapi/getncchanges.c:2919: DsGetNCChanges 2nd replication