Displaying 5 results from an estimated 5 matches for "82b24c02".
2020 Nov 17
7
changes on DC not replicated, while showrepl reports no issues
...means. I hope someone here is able to explain..?
>
> It's output:
>
>> root at dc2:~# samba-tool drs uptodateness
>> 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 ID e50c4440-f3d2-429e-a19d-c11bc72f5565
>> Unknown invocation ID 556b2cb4-e576-48e2-bb7c-7f62caee84fc
>> Unknown invocation ID 7281ff0f-5af2-4ded-bdaf-362f1545d221...
2020 Nov 17
0
changes on DC not replicated, while showrepl reports no issues
...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 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 ID e50c4440-f3d2-429e-a19d-c11bc72f5565
> Unknown invocation ID 556b2cb4-e576-48e2-bb7c-7f62caee84fc
> Unknown invocation ID 7281ff0f-5af2-4ded-bdaf-362f1545d221
> Unknown in...
2020 Nov 17
0
changes on DC not replicated, while showrepl reports no issues
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 ID e50c4440-f3d2-429e-a19d-c11bc72f5565
> >>> Unknown invocation ID 556b2cb4-e576-48e2-bb7c-7f62caee84fc
> >>> Unknown invocation ID...
2020 Nov 16
6
changes on DC not replicated, while showrepl reports no issues
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
2014 Jul 01
1
sudden replication failures
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
Default-First-Site-Name\DC1 via RPC
DSA object GUID: 81a27497-bdfb-4977-9874-675bbfba490f
Last attempt @ Tue Jul 1 20:58:53 2014 CEST failed, result 8442
(WERR_DS_DRA_INTERNAL_ERROR)
825 c...