similar to: WERR_BAD_NET_RESP on replication

On 20/09/2020 00:30, Elias Pereira via samba wrote: > hi, > > I listed the 0ADEL entries with the command below and didn't find the > object. > # ldbsearch --cross-ncs --show-deleted -H /var/lib/samba/private/sam.ldb | > grep "\0ADEL" > > I tried to delete using the command below, but it says it doesn't exist. > # ldbdel -H

hi, I listed the 0ADEL entries with the command below and didn't find the object. # ldbsearch --cross-ncs --show-deleted -H /var/lib/samba/private/sam.ldb | grep "\0ADEL" I tried to delete using the command below, but it says it doesn't exist. # ldbdel -H /var/lib/samba/private/sam.ldb "<GUID=44b7fb44-1a88-42a4-854b-60bddd391577>" --show-deleted --relax delete

> > Well, you wouldn't be able to delete it, how can you delete something that has already been deleted :-) Samba's ghosts... O.o :D Try running this: samba-tool domain tombstones expunge --tombstone-lifetime=1 Ok, this error was fixed!! Thanks Rowland!! But, the error with the replication still occurs. I thought the replication error was linked to the ghost entry error. #

On Thu, 2024-04-11 at 14:21 -0300, Elias Pereira wrote: > Hello?Andrew, > > 1. What is the explanation for the fact that when the log level is > set to 5 or 7, the NT_STATUS_IO_TIMEOUT error does not appear, but > when it is at the default log level, it does? I don't have an explanation for this, sorry. ?Have you looked into the 1.5 second queries, what is sending them and

Hello, We have some computers from a lab that the operating system is ubuntu and are in the domain. I need the "alunos" group to have permissions in the tty and dialout group, since they need to use some arduinos. I have tried the following: net groupmap add ntgroup=alunos sid=1121 type=domain unixgroup=tty net groupmap add ntgroup=alunos sid=1121 type=domain unixgroup=dialout But

No errors occur, but still not replicating. It is not of all entries. For example, there are some users that the groups they are part, differ between the two DCs. In the link below there is a diff between groups of a specific user. # ldbsearch -H /var/lib/samba/private/sam.ldb "(samAccountName=125202)" memberOf | grep CN= | awk -F, '{ print $1 }'

Regarding the groups, now it's all right. Another doubt is about this bydefaults entry. The dc4 has this entry, but the dc3 does not. The dc3 is the fmso roles guy. Does it work that way or is there something wrong there? * Comparing [DOMAIN] context... * DN lists have different size: 5702 != 5703 * DNs found only in ldap://DC4:

> > The question has to be, why do you only have it on one DC ? I am also asking myself this question because the dc3 was the first one I provisioned. Ok. Somehow this was removed. Would it be possible to recreate this entry or the best thing to do is to change the roles to dc4 and provision another DC instead of dc3? On Mon, Sep 21, 2020 at 11:13 AM Rowland penny via samba < samba at

On 20/09/2020 15:31, Elias Pereira via samba wrote: >> But, the error with the replication still occurs. I thought the replication >> error was linked to the ghost entry error. >> # samba-tool drs replicate DC3 DC4 dc=campus,dc=company,dc=br --full-sync >> --sync-forced >> ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - >>

On 21/09/2020 00:35, Elias Pereira via samba wrote: > No errors occur, but still not replicating. It is not of all entries. > > For example, there are some users that the groups they are part, differ > between the two DCs. > > In the link below there is a diff between groups of a specific user. > # ldbsearch -H /var/lib/samba/private/sam.ldb "(samAccountName=125202)"

On 21/09/2020 15:00, Elias Pereira via samba wrote: > Another doubt is about this bydefaults entry. > The dc4 has this entry, but the dc3 does not. The dc3 is the fmso roles guy. > Does it work that way or is there something wrong there? Whilst there are a few attributes that do not replicate, all DN's should. > * Comparing [DOMAIN] context... > > * DN lists have different

On 21/09/2020 15:23, Elias Pereira via samba wrote: >> The question has to be, why do you only have it on one DC ? > > I am also asking myself this question because the dc3 was the first one I > provisioned. > > Ok. Somehow this was removed. Would it be possible to recreate this entry > or the best thing to do is to change the roles to dc4 and provision another > DC

Hi, Many of these syncing problems were solved in Samba 4.7 (and probably a few more in 4.8). There were a number of unresolved locking issues that we uncovered as well as some inconsistencies with Windows replication. I would try join a DC with one of the latest Samba versions and see if your problems persist. Cheers, Garming On 21/06/18 21:35, Chris Lewis via samba wrote: > Hello, >

Hi ! Since few months, dreplsrv is eating lots of memory in few days. Within 2 weeks, the process is generaly OOM killed and replication become weired. I need to restart samba-ad-dc. Here is my config : - Samba 4.11.6 / 4 vcpu / 2Go Ram - 10215 objects (ldbs file = 300MB) This memory problem only happen on my headbridge DC (star topolgy with 20 DC) If I add some ram, the

upgrade one of 2 DCs from 4.10 to 4.11.6 seems to work, I wonder about these messages: M?r 05 09:06:21 adc1 samba[4198]: task[dreplsrv][4198]: [2020/03/05 09:06:21.737684, 0] ../../source4/dsdb/repl/drepl_notify.c:353(dreplsrv_notify_check) M?r 05 09:06:21 adc1 samba[4198]: task[dreplsrv][4198]: dreplsrv_notify_check: Failed to load repsTo for

What does the WERR_BAD_NET_RESP means? I'm currently upgrading our DCs to 4.8.3 and I've noticed that the off-site DC has a sync problem of the CN=Configuration NC. The FSMO DC is still in the 4.5.5, but all other DCs, including the off-site are already on 4.8.3. Trying to sync the off-site DC with one of the updated DCs does not work either. The WERR_BAD_NET_RESP message already

Hi, I've setup Samba NT based networks with OpenLDAP database. But to make sambas operations works fetching data to LDAP, it should have an account on LDAP that able to write some objects, such as passwords (when changing passwd) or object creation (when registering or joining to directory) .The scope of this account is strong enough to any containers on the directory, such as

Hi list, I just upgraded my Samba AD DC to v4.9.4. Unfortunately, I can't recall which version I had before that, I believe it must have been something between 4.6 and 4.8. Anyway, now that the upgrade is done, it looks like DNS is gone. Host commands are timing out, netstat reveals that no process is listening on :53. Other than that, Samba is starting and working fine. I can list shares,

Hello, We have a Windows 2008 DC (inview-dc1 and a samba 4.4.16 (inview-dc2) server as a backup DC. The system for the most-part works OK, but occasionally the Samba DC goes wildly out of sync (with respect to group membership), normally after a change to a large group. I have noted previously before the out-of-sync event occurs, this command always fails thus : root at inview-dc2:~#

Thanks Garming. We currently use a standalone bind DNS server. Will the later version of samba work without the integrated DNS backend? Cheers Chris On 21/06/18 23:41, Garming Sam wrote: > Hi, > > Many of these syncing problems were solved in Samba 4.7 (and probably a > few more in 4.8). There were a number of unresolved locking issues that > we uncovered as well as some