Displaying 20 results from an estimated 200 matches similar to: "After updating"
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
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 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
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 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
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 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
2014 Oct 30
1
Missing dns.keytab and named.conf
Hello list:
I would like change the dns backend from Samba Internal DNS to
BIND_DLZ . I compiled samba 4.1.7 on debian wheezy. But when I did
the tutorial https://wiki.samba.org/index.php/DNS_Backend_BIND I
noticed that there was no file /usr/local/samba/private/named.conf nor
dns.keytab. I found a file named on
/usr/local/samba/share/setup/named.conf but I'm not sure that's the
2016 Mar 12
4
samba-4.3.6 and talloc-2.1.6
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
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
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 May 25
1
LDAP broken after AD DC upgrade from 4.7 to 4.8
Hi *,
I just upgraded my AD DC from 4.7.6 to 4.8.1. (Arch Linux)
After a reboot my LDAP database is almost empty, when accessed from a
LDAP browser or dsa.msc.
samba-tool dbcheck --fix fails as even LostAndFound isn't there anymore.
ERROR(ldb): uncaught exception - descriptor_modify on
CN=SERVER,CN=LostAndFound,DC=dschungel,DC=local failed: No such Base DN:
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
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
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 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
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 30
4
possible memory leak in ldb module while dbcheck on RODC
An embedded and charset-unspecified text was scrubbed...
Name: memory_profiler.txt
URL: <http://lists.samba.org/pipermail/samba/attachments/20170330/f5d10ac9/memory_profiler.txt>
2014 Jul 24
0
Fwd: Re: Fwd: dnsdomainzone replication failure
-------- 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
2019 Jul 03
2
`samba-tool dbcheck --cross-ncs --fix` fails: governsID already exists as an attributeId or governsId
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: