similar to: samba_kcc RODC failes with NT_STATUS_ACCESS_DENIED

I would have assumed that deleting all the NTDS connections for all the DCs would have remedied this issue. I'll write a patch to try to avoid this error in any case. Ignoring this error and answering your earlier question, it's often hard to tell if the KCC is doing what is expected or not. To figure that out, you need a lot more information about the network topology configuration,

On 9/18/2016 6:23 PM, Garming Sam wrote: > Hi, > > For the unsorted attributeID values errors, can you first try: > > samba-tool dbcheck --cross-ncs --fix --yes 'fix_replmetadata_unsorted_attid' > > There's too much going on, and it does look like it might be bailing > out. Running it with 'fix_replmetadata_unsorted_attid' should fix those > first

Hello list, I try to fix my issue and found some more debug information: 1) I see error in this situation: Default-First-Site-Name: - TEST-DC (RWDC) Testsite2: - empty Testsite: - BUILDHOST (RODC) If I move TEST-DC to Testsite2, it fix the error, maybe because of 2). 2) python/samba/kcc/__init__.py:create_connections function try always to connect to Default-First-Site-Name, although

On 9/21/2016 11:32 PM, Garming Sam wrote: > I would have assumed that deleting all the NTDS connections for all the > DCs would have remedied this issue. I'll write a patch to try to avoid > this error in any case. > > Ignoring this error and answering your earlier question, it's often hard > to tell if the KCC is doing what is expected or not. To figure that out, >

Hello Rowland, of course it will be started by samba, I saw this output if I run "samba -i". But I can trigger this output also by starting samba_kcc manually. Andrej -----Ursprüngliche Nachricht----- Von: Rowland Penny [mailto:rpenny at samba.org] Gesendet: Donnerstag, 9. November 2017 14:04 An: samba at lists.samba.org Cc: Andrej Gessel <Andrej.Gessel at janztec.com>

Hello, I'm trying to promote samba4 as a 3rd DC in Windows 2008 R2 AD domain (to get rid of Windows Servers in future). It's joined well, but failing on samba_kcc run (it's happened when I launched samba after joining the domain, so for debugging purposes I then started samba_kcc manually): # /usr/local/samba/sbin/samba_kcc Traceback (most recent call last): File

@Rowland. I now see he only mailed me. Here you go.. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: Alex [mailto:samba at abisoft.biz] > Verzonden: maandag 10 februari 2020 14:53 > Aan: L.P.H. van Belle > Onderwerp: Re: [Samba] samba_kcc issue after joining the > domain as a DC > > Hello L.P.H., > > Thank you for your quick reply! > > >

Hello, I am getting these errors in /var/log/messages : Oct 12 16:36:15 sambadc samba[7147]: [2013/10/12 16:36:15.817541, 0] ../source4/dsdb/kcc/kcc_periodic.c:664(kccsrv_samba_kcc) Oct 12 16:36:15 sambadc samba[7147]: Calling samba_kcc script Oct 12 16:36:15 sambadc abrt: detected unhandled Python exception in '/usr/local/samba/sbin/samba_kcc' Oct 12 16:36:15 sambadc

Hello, Updated samba from 4.4.5 to 4.5.0. All DC's are Ubuntu 12.04.5 LTS. I install samba from source(./configure,make,make install). Looking at the release notes I see the section on "replPropertyMetaData Chnages". I run 'samba-tool dbcheck --cross-ncs --fix --yes' and see the errors and samba attempts to fix. ERROR: unsorted attributeID values in

Hi samba list!!! Douglas, /usr/sbin/samba_kcc is made in python. Does it have a link to source4/dsdb/kcc/kcc_periodic.c which is made in C? The errors that appear in my DCs have their output in the C code. Correct me if I'm wrong, but I read in some old posts on the list that samba would have a new code for kcc (python code?), which would be closer to what M$ uses. Could this have anything

hi, The error is consistently occurring across all four of my DCs. [2024/01/19 14:02:05.917120, 0] source4/dsdb/kcc/kcc_periodic.c:790(samba_kcc_done) source4/dsdb/kcc/kcc_periodic.c:790: Failed samba_kcc - NT_STATUS_IO_TIMEOUT I configured logging to level 5 and observed DC1. No errors were detected; instead, kcc_periodic.c executed smoothly, and the system reported a successful outcome.

hi, *EDIT*: Every 2 hours kcc_periodic.c is executed The error occurs on all 4 of my DCs: [2024/01/19 14:02:05.917120, 0] source4/dsdb/kcc/kcc_periodic.c:790(samba_kcc_done) source4/dsdb/kcc/kcc_periodic.c:790: Failed samba_kcc - NT_STATUS_IO_TIMEOUT Today I enabled logging at level 5 and monitored DC1. There was no error, on the contrary, kcc_periodic.c ran correctly and the message was Ok.

The two systems I'm referring to are on different domains, different locations. No connection whatsoever except me being the one administering both. According to oEMInformation the server was provisioned by 4.3.3. I just checked the Samba log file and it seems that version 4.7.4 was running before the update. I'm now looking at the logs right before the upgrade and indeed, there have

hi, Every 2 hours run kcc_periodic.c The error occurs on all 4 of my DCs: [2024/01/19 14:02:05.917120, 0] source4/dsdb/kcc/kcc_periodic.c:790(samba_kcc_done) source4/dsdb/kcc/kcc_periodic.c:790: Failed samba_kcc - NT_STATUS_IO_TIMEOUT Today I enabled logging at level 5 and monitored DC1. There was no error, on the contrary, kcc_periodic.c ran correctly and the message was Ok. [2024/01/19

After getting the below errors I investigated by building samba on a vm and restoring a backup to that VM and I did not get the same errors. It seems that when you run sudo make install that the below shared libraries do not get replaced and that is what is causing the errors. Am I missing something? I am currently running 4.12.6. /usr/local/samba/sbin/samba_dnsupdate: ldb: unable to dlopen

Ok, you have found something, and i've seen a bit more. First, this. /usr/bin/samba_kcc: ImportError: /usr/lib/samba/libreplace-samba4.so: version `SAMBA_4.7.4' not found (required by /usr/lib/libsamba-util.so.0) [2018/12/22 19:13:45.004497, 0] There are left overs from a previous install. You are on Arch Linux as i did read. With what i've seen. Stop samba and all related

Either the local server is busy, or possibly (but it would not explain the samba_kcc) Samba's drepl process is stuck talking to a remote server. Is the drepl local processes very busy doing inbound replication? My instinct is either the server is very busy (and this should show up in CPU use) or a transaction is being held open excessively. Andrew Bartlett On Sat, 2024-03-09 at 19:11 -0300,

... I see this on a 4.8.4 debian DC Aug 31 20:10:19 adc2 samba[657]: task[kccsrv][657]: /usr/sbin/samba_kcc: ldb_wrap open of secrets.ldb Aug 31 20:15:19 adc2 samba[657]: task[kccsrv][657]: [2018/08/31 20:15:19.413299, 0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) Aug 31 20:15:19 adc2 samba[657]: task[kccsrv][657]: /usr/sbin/samba_kcc: ldb_wrap open of secrets.ldb It seems not

I'm sorry, after double-checking the Louis's link I've found that the domain zone should be domain-wide, while the _msdcs stuff should be forest wide. I'll change it and try again. Apologies. >>>>> # samba-tool dns zonelist 172.26.1.81 >>>>> Password for [administrator at domain.com]: >>>>> 2 zone(s) found >>>>>

I've been grappling with a recurring set of errors for quite some time now: - UpdateRefs failed with NT_STATUS_IO_TIMEOUT - Failed samba_kcc - NT_STATUS_IO_TIMEOUT - IRPC callback failed for DsReplicaSync - NT_STATUS_IO_TIMEOUT Despite cranking up the log level to 10, the returned information remains frustratingly cryptic and hard to decipher. This error, being overly generic, continues to