similar to: LDAP broken after AD DC upgrade from 4.7 to 4.8

Hello list, today I updated my samba domain to version 4.9, after everything went well, I ran the command ./samba-tool dbcheck and the error is the following, however everything else works perfect ... that could be happening???? ./samba-tool dbcheck Checking 903 objects ERROR(): uncaught exception - 'ascii' codec can't encode character u'xe1' in position 313: ordinal not in

Hello all; I use CentOS 7.5.1804 I update from samba-4.8.2 to samba-4.9.1 and finish with not errors, but when I run samba-tool dbcheck --cross-ncs I have the error: [root at gtmad ~]# samba-tool dbcheck --cross-ncs Checking 4087 objects ERROR(<type 'exceptions.UnicodeEncodeError'>): uncaught exception - 'ascii' codec can't encode character u'\xe9' in

I build new version of talloc-2.1.6 (build from external tarball) and samba-4.3.6. But if I provision domain by command samba-tool domain provision --realm=test.alt --domain test --adminpass='Pa$$word' --dns-backend=SAMBA_INTERNAL --server-role=dc --use-rfc2307 --use-xattrs=yes I got error: Fixing provision GUIDs ERROR(runtime): uncaught exception - pytalloc_reference_ex() called for

Hello, we have 2 DC with Sernet Samba-packages 4.9.4 if we do a "samba-tool dbcheck" we get the following error: ---------- samba-tool dbcheck Checking 1631 objects ERROR(<type 'exceptions.UnicodeDecodeError'>): uncaught exception - 'ascii' codec can't decode byte 0xc3 in position 29: ordinal not in range(128) File

I just tested Samba 4.9.2 on one of my DCs, previously running version 4.8.6. Immediately after install, I ran "samba-tool dbcheck" and got the following: Checking 511 objects ERROR(<type 'exceptions.UnicodeDecodeError'>): uncaught exception - 'ascii' codec can't decode byte 0xc3 in position 25: ordinal not in range(128)   File

I decided to give Samba 4.9.x a new try as AD DC in one of my servers. It has been running version 4.8.9. I installed version 4.9.4 and when I ran samba-tool dbcheck I still obtained the following error message: ERROR(<type 'exceptions.UnicodeDecodeError'>): uncaught exception - 'ascii' codec can't decode byte 0xc3 in position 25: ordinal not in range(128)   File

Hi Louis, Am 28.02.2019 12:47, schrieb L.P.H. van Belle via samba: > Hai Stefan, > > See. > https://bugzilla.samba.org/show_bug.cgi?id=13616 > That's what I found, too. We did not do an update it's a fresh installation (migrate from samb3 with classicupgrade). I now did a "samba-tool dbcheck -v " and I see that the "ü" in the DN of a OU it's the

dpkg -l |grep ldb You want to see : libldb1 I think its 1.4.3 you will see, thats the version im having also atm. The bugnr is not in the release notes, so i expect this in the next release to be corrected. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Stefan Kania via samba > Verzonden: donderdag 28

Hi, We migrated from Samba 3 to 4 (4.6.7-Ubuntu) and added promoted a Server 2008R2 as a Domain Controller. We've come across the following issues and request some suggestions to resolve them - The migration didn't generate DNS entries for the new realm. We had to manually create a new zone file (/var/cache/bind) for the new realm. Only then we were able to promote the

It's amazing how long Samba just keeps running even when apparently everything's broken. In preparation of finally upgrading our DCs to 41.0, I ran dbcheck on all of them, resulting in: graz-dc-sem: > Checking 3861 objects > Error: governsID CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on 1.3.6.1.4.1.19414.3.2.2 already exists as an attributeId or governsId > Error:

Hi Andrew, The realm infact has no dots, is this going be an issue? It is different to workgroup. The details did get "Lost in Redaction" Coming back to the DNS. When we did the domain migration , we used --dns-backend=BIND9_DLZ. My assumption was it will stick to the BIND_DLZ. Anyhow, when we use the default settings post migration, we are not able to DCPROMO the Server 2008R2 server.

Here is the information requested it took 3 days before results came samba-tool dbcheck finished with this error root at ham1:/usr/local/samba/bin# time ./samba-tool dbcheck --cross-ncs Checking 212687 objects ERROR(<type 'exceptions.MemoryError'>): uncaught exception - File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run

Am 24.07.2014 10:53, schrieb C.Kindler: > > Hello Achim, > > having similar troubles as mentioned on > https://lists.samba.org/archive/samba/2014-July/182916.html in our domain > > > How to solve the replication error? > > Many thanks, > Chris > > ---------- Forwarded message ---------- > From: *C.Kindler* <kindc1 at gmail.com <mailto:kindc1 at

Hai Andrej, Oeps, Sorry, my mistake 4.6.x needs at least 1.1.29. But you can upgrade to 4.6.x ;-) Check again and if that problem then still exists, then i think you can better ask this one in the samba-technical list. Or if Rowland knows something more about this. One tip, wait untill tomorrow or the weekend, there wil be a new release due to the regression bug. There planning is to be

Hi all, I have tried to update one of our samba servers from the currently installed version 4.8.6 to the latest 4.9git release. Compilation and installation went through without any errors but when I do a dbcheck before the initial start of the new version I do get the following error:  /usr/local/samba/bin/samba-tool dbcheck --cross-ncs --verbose ....... ERROR(<type

Dne 2019-03-25 16:02, Rowland Penny via samba napsal: > On Mon, 25 Mar 2019 15:12:16 +0100 > franta via samba <samba at lists.samba.org> wrote: > >> Hi team, >> I have Samba (4.9.5) AD DC, and when trying to add second DC, join >> fail: >> >> # samba-tool domain join zamecek.home DC >> -U"SSUPS-ZAMECEK\administrator"

-------- Original-Nachricht -------- Betreff: Re: Fwd: dnsdomainzone replication failure Datum: Thu, 24 Jul 2014 13:32:56 +0200 Von: C.Kindler <kindc1 at gmail.com> An: Achim Gottinger <achim at ag-web.biz> Many thanks! I didnt thought about Microsoft Admin Tools :-) - Yes with this is much easier: Now the replication goes a little forward: in the logs there are now such

>> It might help if you tell us what your actual './configure' was ? >> Something else might be pulling in the requirement for lmdb. Here it goes: ./configure -j 8 --with-systemd --with-statedir=/usr/local/samba/var --with-privatedir=/usr/local/samba/var/private --with-logfilebase=/usr/local/samba/var/log --with-privileged-socket-dir=/usr/local/samba/var/lib Also, after I

On 08-11-2018 21:02, Rommel Rodriguez Toirac via samba wrote: > Hello all; > I use CentOS 7.5.1804 > I update from samba-4.8.2 to samba-4.9.1 and finish with not errors, but when I run > > samba-tool dbcheck --cross-ncs > > I have the error: > > [root at gtmad ~]# samba-tool dbcheck --cross-ncs > Checking 4087 objects > ERROR(<type

On Thu, 13 Sep 2018 14:41:54 +0100 miguel medalha via samba <samba at lists.samba.org> wrote: > Hello > > In one of my DCs, when I run ./configure for Samba 4.9.0, it fails > with the following message: > > Checking for lmdb >= 0.9.16 via header check : not > found Samba AD DC and --enable-selftest requires lmdb 0.9.16 or later > > My ./configure command