similar to: samba4 replication issues | sam.ldb inconsistency

Displaying 20 results from an estimated 5000 matches similar to: "samba4 replication issues | sam.ldb inconsistency"

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
2017 Oct 09
4
samba getting stuck, highwatermark replication issue?
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 common cause. For the rest, the systems appear fine, enough diskspace, nothing
2017 Oct 10
2
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
2017 Oct 17
2
possible to use ldbedit in a safe way
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
2017 Oct 16
5
possible to use ldbedit in a safe way
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
2017 Oct 10
0
samba getting stuck, highwatermark replication issue?
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
2017 Oct 09
0
samba getting stuck, highwatermark replication issue?
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
2017 Oct 17
2
possible to use ldbedit in a safe way
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 -
2014 Jul 07
0
corrupt sam.ldb on a dc
Hi all, On one of my two (sernet 4.1.7) domain controllers, I seem to have a corrupt sam database: root at dc1:~# samba-tool dbcheck --cross-ncs ltdb: tdb(/var/lib/samba/private/sam.ldb.d/DC=DOMAINDNSZONES,DC=SAMBA,DC=COMPANY,DC=COM.ldb): tdb_rec_read bad magic 0x198 at offset=1044437120 ERROR(ldb): uncaught exception - Indexed and full searches both failed! File
2017 Oct 17
0
possible to use ldbedit in a safe way
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
2012 Sep 15
0
Samba4 AD returning incomplete results, can't edit much, and unable to reindex sam.ldb
Not sure if this is best sent to samba or samba-technical. If an admin thinks this is best sent to technical, let me know and I'll resend it there. Hi all, Well I've managed to land myself in a bit of a heap. I've been successfully running Samba4 at two schools I administer as well as my home test network, starting with alpha17 and now on beta8. Group Policy works a charm. But
2017 Aug 26
2
DC Upgrade from 4.1.7 to 4.6.7
> -----Message d'origine----- > De : Andrew Bartlett [mailto:abartlet at samba.org] > Envoyé : samedi 26 août 2017 12:40 > À : HB; samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > > On Sat, 2017-08-26 at 12:32 +0400, HB via samba wrote: > > > > > Here is the output of samba-tool dbcheck : > > # samba-tool dbcheck >
2018 Jul 31
2
samba-tool dbcheck "Indexed and full searches both failed"
On Tue, 31 Jul 2018 07:37:38 -0500 Denis Morejon via samba <samba at lists.samba.org> wrote: > Hi: > > I have two samba 4.7.4 DCs. One of them has problems. I can not use > samba-tool on it. Then, when I try to fix It's database It returns: > > ------------------------------------------------------------------------------------------------------------------- >
2016 Jul 28
3
DomainDnsZones inbound replication issue
Greetings, I am having a problem with one of my DCs (DC3) replicating DomainDnsZones. On DC3 replication is successful on both Inbound and Outbound with both of my other DCs. On both of my other DCs (DC1 & DC2) I only get a failure with Inbound replication for DomainDnsZones from DC3 with a result 8442 (WERR_DS_DRA_INTERNAL_ERROR). If I try to force replication to DC3 from DC1 using
2023 Mar 03
2
DomainDnsZones bad magic
I've been called back to an old workplace to try to help with some issues that they have and have found that the DomainDnsZones database is not replicating. Everything else in the replication seems to be fine. I ran a samba-tool dbcheck on the affected server and it returns: ltdb: tdb(/var/lib/samba/private/sam.ldb.d/DC=DOMAINDNSZONES,DC=MYDOMAIN,DC=MYCOMPANY.ldb): tdb_rec_read bad magic
2017 Aug 26
2
DC Upgrade from 4.1.7 to 4.6.7
> -----Message d'origine----- > De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland > Penny via samba > Envoyé : samedi 26 août 2017 12:00 > À : samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > ... > On Sat, 26 Aug 2017 11:28:00 +0400 > > Hi, > > > > I have begun to add a new 4.6.7 DC (following
2018 Jul 31
2
Internal DNS migrate to Bind9_DLZ
On Tue, 31 Jul 2018 11:39:56 +0200 Michal <Michal67M at seznam.cz> wrote: > > /etc/named.conf > > # Global Configuration Options > > > > include "/var/lib/samba/bind-dns/named.conf"; > > > > options { > > > > dump-file "/var/named/data/cache_dump.db"; > > statistics-file
2017 Aug 26
2
DC Upgrade from 4.1.7 to 4.6.7
> -----Message d'origine----- > De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland > Penny via samba > Envoyé : lundi 21 août 2017 16:34 > À : samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > > On Mon, 21 Aug 2017 15:52:01 +0400 > HB via samba <samba at lists.samba.org> wrote: > > > Hello all,
2014 Jul 22
1
tdb_rec_read bad magic
using samba 4.1.4 syslog have alot of those in log: [2014/07/22 13:24:12.22351, 0] ../lib/ldb-samba/ldb_wrap.c:71(ldb_wrap_debug) ldb: ltdb: tdb(/usr/local/samba/private/sam.ldb.d/DC=DOMAINDNSZONES,DC=MYDOMAIN,DC=LOCAL.ldb): tdb_rec_read bad magic 0x0 at offset=516897176 Anything I can do to fix it?
2023 Mar 03
1
DomainDnsZones bad magic
On 03/03/2023 19:36, Peter Pollock via samba wrote: > I've been called back to an old workplace to try to help with some issues > that they have and have found that the DomainDnsZones database is not > replicating. Everything else in the replication seems to be fine. > > I ran a samba-tool dbcheck on the affected server and it returns: > > ltdb: >