similar to: after samba update to 4.9 GIT issue with samba-tool dbcheck

Displaying 20 results from an estimated 500 matches similar to: "after samba update to 4.9 GIT issue with samba-tool dbcheck"

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
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 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 Sep 13
0
[Announce] Samba 4.9.0 Available for Download
>> 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
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 24
5
Samba 4.7.9 dbcheck error
Hello list, I'm getting a weird error message regarding our file server when i run dbcheck on my dc01 running Samba v4.7.9. The error only occurs on dc01, dc02 is fine, the file server also works fine but I want to clean the database before doing the upgrade to version 4.9 dc01:~# samba-tool dbcheck --cross-ncs Checking 4503 objects SID S-1-5-21-3258148492-1502286889-3538134041-1601 for
2018 Sep 13
2
[Announce] Samba 4.9.0 Available for Download
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
2017 Mar 31
0
possible memory leak in ldb module while dbcheck on RODC
What is the ldb version your using? You need : 1.1.29 with samba 4.5.7. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Andrej Gessel via > samba > Verzonden: vrijdag 31 maart 2017 8:55 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] possible memory leak in ldb module while dbcheck on > RODC >
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
2017 Feb 08
1
samba-tool dbcheck uncaught exception
Hello, my domain is Dns domain = foo Realm = FOO Workgroup = FOO samba-tool dbcheck --cross-ncs --fix -v .... Checking object DC=foo ERROR(<type 'exceptions.ValueError'>): uncaught exception - unable to parse dn string File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 175, in _run return self.run(*args, **kwargs) 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
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
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)
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 Jul 03
0
`samba-tool dbcheck --cross-ncs --fix` fails: governsID already exists as an attributeId or governsId
On 03/07/2019 15:50, Sven Schwedas via samba wrote: > 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
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
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
2017 Mar 31
2
possible memory leak in ldb module while dbcheck on RODC
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