similar to: samba-tool dbcheck uncaught exception

Displaying 20 results from an estimated 2000 matches similar to: "samba-tool dbcheck uncaught exception"

2018 Nov 13
0
Error running "samba-tool dbcheck" after going from 4.8.6 to 4.9.2
On Mon, 2018-11-12 at 20:36 +0000, Noel Power wrote: > Hi > > On 09/11/2018 10:21, Andrew Bartlett wrote: > > On Fri, 2018-11-09 at 11:46 +0300, Taner Tas via samba wrote: > > > > 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
2019 Mar 05
2
samba-tool dbcheck: UnicodeDecodeError' with Samba 4.9.4
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
2019 Feb 28
3
samba-tool dbcheck Unicode-Error
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
2019 Feb 28
1
samba-tool dbcheck Unicode-Error
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
2018 Nov 08
3
Error running "samba-tool dbcheck" after going from 4.8.6 to 4.9.2
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
2018 Nov 09
0
Error running "samba-tool dbcheck" after going from 4.8.6 to 4.9.2
> 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 >
2019 Feb 28
0
samba-tool dbcheck Unicode-Error
Hai Stefan, See. https://bugzilla.samba.org/show_bug.cgi?id=13616 I think thats you problem, at least simular. A left over from the python2 -> python3 conversion. I dont know it this one is in the sernet packages. Whats your ldb version? That should tell me more. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org]
2019 Mar 05
0
samba-tool dbcheck: UnicodeDecodeError' with Samba 4.9.4
I had the same problem, it was the DN of one of my OU? I remplaced the "ü" with a "ue" and everything was fine. Am 05.03.19 um 18:10 schrieb miguel medalha via samba: > 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
2019 Feb 28
1
samba-tool dbcheck Unicode-Error
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
2018 Feb 06
0
Samba Migration and AD integration
On Tue, 2018-02-06 at 03:05 +0000, Praveen Ghimire via samba wrote: > 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
2018 Feb 06
1
Samba Migration and AD integration
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.
2018 Feb 06
5
Samba Migration and AD integration
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
2024 Jul 17
1
dbcheck gets uncaught exception
> Anything after the 'Join failed' can be ignored, it is just an > artefact of the cleanup. > > I posted this: > > Do not remove the existing database, well not unless you want to > recreate your domain. > > I will amend it: > > Do not touch 'DC=DOMAINDNSZONES,DC=COMPANY,DC=INTRA.ldb' (or any of the > other files in the same directory)
2018 Oct 19
1
after samba update to 4.9 GIT issue with samba-tool dbcheck
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
2018 Nov 08
0
Error in samba-tool dbcheck after updating to samba-4.9.1
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
2018 Nov 08
4
Error in samba-tool dbcheck after updating to samba-4.9.1
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
2018 Nov 09
0
Error in samba-tool dbcheck after updating to samba-4.9.1
El 8 de noviembre de 2018 4:02:52 PM GMT-05:00, Rommel Rodriguez Toirac via samba <samba at lists.samba.org> escribió: > 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
2018 Sep 16
1
After updating
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
2020 Feb 09
0
Error in samba-tool dbcheck
Hello. We're in the process of migrating an old Samba3 domain to Samba4. Everything is (seem to be?) going ok in our test migration, but we're finding this issue when running samba-tool dbcheck --cross-ncs Checking 15131 objects ERROR(<class 'IndexError'>): uncaught exception - index out of range File
2014 Jul 24
0
Fwd: dnsdomainzone replication failure
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