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

Hi Rowland, On 10/16/2017 05:13 PM, Rowland Penny via samba wrote: > If you need to edit the NCs in sam.ldb.d, use '--cross-ncs' with the > ldb command, this allows you safely change things. There have been > reports of AD being destroyed by directly editing the ldb's in sam.ldb.d Looking at the man page of ldbedit, I see no reference to --cross-ncs Tried: > ldbedit

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

Am 25.11.2017 um 16:55 schrieb Achim Gottinger via samba: > > > Am 25.11.2017 um 04:39 schrieb Andrew Bartlett: >> On Fri, 2017-11-24 at 11:55 +1300, Andrew Bartlett via samba wrote: >>> On Tue, 2017-11-21 at 11:21 +0100, Achim Gottinger via samba wrote: >>>> Hello List, >>>> >>>> In preparation to update my samba ad-dc's running

Hi colleagues, it seems i've hit a bug in SAMBA as follows: The local windows network admin of our local radio station filled / transferred some user account data into our new FreeNAS by the Win RSAT. We are setting up SAMBA as a PDC incl. directory service and use the current stable FreeNAS with its current SAMBA "4.3.6-GIT-UNKNOWN" One account name "produktion-a"

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

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 ./CN=CONFIGURATION,DC=SAMBA,DC=COMPANY,DC=COM > > to remove them. > > While that seems to have worked

On Tue, 22 Jan 2019, Rowland Penny via samba wrote: > On Tue, 22 Jan 2019 14:20:21 -0500 (EST) > "Vincent S. Cojot via samba" <samba at lists.samba.org> wrote: > >> >> Hi All, >> >> On my two-DC setup (dc00 and dc01 - Used to be a 4-Dc setup but 02 >> and 03 are gone), I've noticed the following errors which I am unable >> to

On Fri, 2017-11-24 at 11:55 +1300, Andrew Bartlett via samba wrote: > On Tue, 2017-11-21 at 11:21 +0100, Achim Gottinger via samba wrote: > > Hello List, > > > > In preparation to update my samba ad-dc's running debian wheezy with > > backported samba 4.6.8 to 4.7.3. > > I'd like to fix two errors showing up in dbcheck whom hab been reported > > by

On Mon, 2017-10-16 at 16:53 +0200, mj via samba 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 Are they breaking anything? If so, can you get me more detail on exactly what breaks? > ldbedit -e nano -H ./CN=CONFIGURATION,DC=SAMBA,DC=COMPANY,DC=COM > > to remove them.

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

Hello List, In preparation to update my samba ad-dc's running debian wheezy with backported samba 4.6.8 to 4.7.3. I'd like to fix two errors showing up in dbcheck whom hab been reported by dbckech --cross-ncs for an long time but without causing any issues so far. I'm getting this error on my main dc root at server:~# samba-tool dbcheck --cross-ncs Checking 4188 objects ERROR: no

On Mon, Jan 22, 2018 at 05:24:44PM +0100, Achim Gottinger via samba wrote: > Am 22.01.2018 um 10:49 schrieb Stefan Metzmacher via samba: > > Also DO NOT repair the following errors with samba-tool dbcheck! > > "Remove duplicate links in attribute" > > and > > "ERROR: orphaned backlink" > > as this removes the ability to repair the database >

Hi, About a year ago (I think I was using v4.2.x at the time), I extended the schema of my Samba AD. This worked just fine and since then I have been able to create and edit objects from my custom schema via ADSIEdit. This worked fine under 4.3.x as well - the last such object I successfully created was just over two months ago, at which point I was running some variant of 4.3.x (probably 4.3.5).

Hi Marc, Thanks for your reply. We are using BIND9_DLZ currently as the DNS backend I manually selected a replication partner (the FSMO roles DC). We do have some errors when doing a dbcheck but I'm not able to fix them. I've detailed this in another post. Here is an example of each type: Example1: *ERROR: incorrect GUID component for member in object

On Tue, 2017-10-17 at 11:04 +0200, mj via samba wrote: > > 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,

> I think it would be easier to: > > ldbedit -e nano -H /var/lib/samba/private/sam.ldb --cross-ncs -b > "DC=1.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDnsZones,DC=samdom,DC=com" > "(DC=21)" > > On a DC. > > Rowland Well, not so simple... I tried ldbedit -e vim -H /usr/local/samba/private/sam.ldb --cross-ncs -b

Hi All, On my two-DC setup (dc00 and dc01 - Used to be a 4-Dc setup but 02 and 03 are gone), I've noticed the following errors which I am unable to fix.. Any hints? * Basic dbcheck is clean. [root at dc00 ~]# samba-tool dbcheck Checking 327 objects Checked 327 objects (0 errors) * Cross-NCS shows two errors related to a de-comissionned DC (dc02) and cannot auto-fix this.. How do I fix

On Wed, 2016-12-07 at 12:23 +0000, Chris Alavoine via samba wrote: > Hi all, > > I've now upgraded to Samba-4.5.2 and I've tried running: > > samba-tool domain tombstones expunge > > but I simpley get: > > Removed 0 objects and 0 links successfully, however I'm still seeing > several hundred errors when running a dbcheck with the "not remocing

Hi all, James, After following James' suggestions fixing the several dbcheck errors, and having observed things for a few days, I'd like to update this issue, and hope for some new input again. :-) Summary: three DCs, all three running Version 4.5.10-SerNet-Debian-16.wheezy, samba-tool dbcheck --cross-ncs reports no errors, except for two (supposedly innocent) dangling forward links