similar to: Replication on 4.19.5 working properly ?

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

On 17/11/2020 14:40, L.P.H. van Belle via samba wrote: > samba-tool visualize uptodateness -r > Does not show out of sync here. > > Rowland, you any ideas on that. > This might be just cosmetic. It appears it is just cosmetic, see my other post. I have asked the person who added it, why he added it, I don't expect a quick reply, he is on the other side of the planet ?

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: >

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

Hai, That looks like its a bug. I just verified this on a 4.10.10 AD-DC. I was hoping a python package was missing but i dont see/have missing packages here. I have exact the same result. I have reported it : https://bugzilla.samba.org/show_bug.cgi?id=14184 Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens >

Hello, I have three Samba Active Directory Domain Controllers that, from all metrics seem to be working just fine, but for one thing: When I run the following command: # samba-tool visualize uptodateness -r I always get the following response: ERROR(<class 'IndexError'>): uncaught exception - list index out of range File

>> >> I was able to get replication working again by deleting DNS records that were conflicting in LDAP. >> >> Used ldapcmp tool to find conflicts >> https://wiki.samba.org/index.php/Samba-tool_ldapcmp >> > > Ok, the problem seems to be back again. > > Ubuntu 16.04, samba 4.9.3 > > I’ve checked with: samba-tool ldapcmp > between dc1

Hai, Can you run this script on a good DC and the problem DC. https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Mail me both files. I'll have a quick check. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens M B via samba > Verzonden: woensdag 24 april 2019 14:48 > Aan: samba at

Release Announcements --------------------- This is the latest stable release of the Samba 4.19 release series. Changes since 4.19.4 -------------------- o? Ralph Boehme <slow at samba.org> ?? * BUG 13688: Windows 2016 fails to restore previous version of a file from a ???? shadow_copy2 snapshot. ?? * BUG 15549: Symlinks on AIX are broken in 4.19 (and a few version before ????

Release Announcements --------------------- This is the latest stable release of the Samba 4.19 release series. Changes since 4.19.4 -------------------- o? Ralph Boehme <slow at samba.org> ?? * BUG 13688: Windows 2016 fails to restore previous version of a file from a ???? shadow_copy2 snapshot. ?? * BUG 15549: Symlinks on AIX are broken in 4.19 (and a few version before ????

Hi, It seems unlikely that the KCC is the cause of these issues. The KCC is only responsible for telling who to connect (and when) and doesn't actually affect any underlying network connectivity. Connectivity between the spokes should not be required and the communication between them is usually just some stale data. But none of that should affect either of these commands. Unless the DRS

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

Hi! I have 2 DC, now add one more DC, but all dcs dont view between they. New DC is "DC2" DC1 - vlan10 -> OK to DC3(Connectad by openvpn) DC1 -> vlan10 -> OK to DC2(vlan50) DC2-> vlan50 -> OK to DC1(vlan10) DC2-> Openvpn -> Dont "see" DC3 DC3 -> Openvpn -> OK to DC1(vlan10) DC3 -> Openvpn -> Dont "view" DC2(vlan50) All version

Hi! Thanks for answer. But, i allowed all ports in my firewall... I tested, shutdown  my DC1 DC2 dont comunication with DC3 I create user in DC2, dont replication with DC3... I waited more in 20 minutes Why ?? Regards; On 17-05-2018 12:01, lingpanda101 wrote: > On 5/17/2018 10:30 AM, Carlos via samba wrote: >> Hi! >> >> I have 2 DC, now add one more DC, but all dcs

Samba 4.5.1 (started with this version as well) I started with 3 domain controllers, DC1 and DC2 at the hub, and another, DC3 as a spoke. Everything was running smoothly with this config. No problems with 'samba-tool drs showrepl'. As soon as I started adding more 'spoke' domain controllers I'm getting timeouts in the 'samba-tool drs showrepl' command. I believe

On 5/17/2018 12:07 PM, Carlos wrote: > Hi! > > Thanks for answer. > > But, i allowed all ports in my firewall... > > I tested, shutdown  my DC1 > > DC2 dont comunication with DC3 > > I create user in DC2, dont replication with DC3... > I waited more in 20 minutes > > Why ?? > > Regards; > > > On 17-05-2018 12:01, lingpanda101 wrote: >>

Hi! In "NTDS settings" created new connection for: DC2 ->DC3 DC3 -> DC2 All OK, I tested with option kccsrv:samba_kcc=No is ok too. But in my DC2, a received one erro: May 17 16:54:44 dc2 samba[10421]: [2018/05/17 16:54:44.543336,  0] ../source4/dsdb/repl/drepl_out_helpers.c:1087(dreplsrv_update_refs_done) May 17 16:54:44 dc2 samba[10421]:   UpdateRefs failed with

I’m getting errors with replication Samba 4.9.3 on Ubuntu 16.04 6 Samba DC’s at 3 sites I recently joined a Win2k8 R2 server to the domain and promoted it to domain controller. The replication was working before that, and not working after. I didn’t realize the problems and tried to join a Win2012 R2 server and promote to DC as well. That also failed with an error about replication failures.

Hello All, WIndows DC reports (not for the entire directory, just a portion. See outputs below). "The replication operation failed because of a schema mismatch between the servers involved.? I suspect the error is a red herring. Running several Samba DCs at multiple sites. Version 4.11.6-Debian from Louis?s repo (on Ubuntu 18) ?vdcw00? is the Windows 2012 R2 server ?cdcx15? is the Samba

On 5/17/2018 3:58 PM, Carlos wrote: > > Hi! > > In "NTDS settings" created new connection for: > > DC2 ->DC3 > > DC3 -> DC2 > > All OK, > > I tested with option > > kccsrv:samba_kcc=No > > is ok too. > > But in my DC2, a received one erro: > > May 17 16:54:44 dc2 samba[10421]: [2018/05/17 16:54:44.543336,  0] >