Andrew Bartlett
2022-Oct-03 21:36 UTC
[Samba] Error domain level command , modul version mismatch
It isn't clear to me exactly where the mixup is happening, but Rowland is exactly on the money, this is an issue with conflicting Samba components. Check you are not mixing a Samba-provided ldb installation with a system provided one, for example, and that there are not other stray Samba components around. Andrew On Fri, 2022-09-30 at 13:34 +0200, Mueller via samba wrote:> I have checked all files in all directories. They are all new with > thetimestamp of the update no old files left! > samba-tool -V4.17.0smbstatus -VVersion 4.17.0samba_dnsupdate -V4.17.0 > > > Could it be it is going with the wrong ldb version? Any idea how I > cantest that? > GreetingsDaniel > > > EDV Daniel M?ller > Leitung EDVTropenklinik Paul-Lechler-KrankenhausPaul-Lechler-Str. > 2472076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499eMail: > mueller at tropenklinik.de > Internet: www.tropenklinik.de > > > > > -----Urspr?ngliche Nachricht-----Von: Rowland Penny via samba > [mailto:samba at lists.samba.org] Gesendet: Freitag, 30. September 2022 > 13:14An: samba at lists.samba.org > Cc: Rowland Penny <rpenny at samba.org>Betreff: Re: [Samba] Error domain > level command , modul version mismatch > > > On 30/09/2022 11:54, Mueller wrote: > > Hello, > > my OS: Debian 11 x64.lsb_release -aNo LSB modules are > > available.Distributor ID: DebianDescription: Debian GNU/Linux 11 > > (bullseye)Release: 11Codename: bullseye > > I updated from samba 4.16.4 straight to 4.17.0. Both Version I > > compiled from source. > > I think what is happening here is that by updating samba in the way > youhave, there are old parts of the original Samba install left. I > wouldsuggest that if you are going to upgrade in this way, you > compile Samba on anew Computer (or VM) and then join this as a new DC > and then, once the newDC is known to be working correctly, demote the > old DC. that way you knowthere is no old components left behind. > > Rowland > > > --To unsubscribe from this list go to the following URL and read > theinstructions: https://lists.samba.org/mailman/options/samba > >-- Andrew Bartlett (he/him) https://samba.org/~abartlet/Samba Team Member (since 2001) https://samba.orgSamba Team Lead, Catalyst IT https://catalyst.net.nz/services/samba Samba Development and Support, Catalyst IT - Expert Open SourceSolutions
I Think it is a bug concerning the ldb version in samba: Bug#998741:
samba-dsdb-modules: Please adjust build-dep version of libldb
So with samba 4.17 it is impossible to compile and install it the right way with
: ldb: module version mismatch in ../../source4/dsdb/samdb/ldb_modules/acl.c :
ldb_version=2.2.4 module_version=2.6.1
ldb: failed to initialise module /usr/lib64/samba/ldb/acl.so : Unavailable
Bad talloc magic value - unknown value <-- it points out it needs another
libldb as installed or does not use the installed one:
On my debian 11 --- apt list libldb*
Auflistung? Fertig
libldb-dev/stable,stable-security 2:2.2.3-2~deb11u2 amd64
libldb2/stable,stable-security,now 2:2.2.3-2~deb11u2 amd64
[Installiert,automatisch]
samba-tool user list
ldb: module version mismatch in ../../source4/dsdb/samdb/ldb_modules/acl.c :
ldb_version=2.2.4 module_version=2.6.1
ldb: failed to initialise module /usr/lib64/samba/ldb/acl.so : Unavailable
Bad talloc magic value - unknown value
==============================================================INTERNAL ERROR:
Signal 6: Aborted in pid 2614 (4.17.0)
If you are running a recent Samba version, and if you think this problem is not
yet fixed in the latest versions, please consider reporting this bug, see
https://wiki.samba.org/index.php/Bug_Reporting
==============================================================
The same Installation working on my debian 10 without any issue:
apt list libldb*
Auflistung... Fertig
libldb-dev/unstable 2:2.5.2+samba4.16.5-1 amd64
libldb1/oldstable,oldstable,now 2:1.5.1+really1.4.6-3+deb10u1 amd64
[Installiert,automatisch]
libldb2/unstable 2:2.5.2+samba4.16.5-1 amd64
root at domslave:~# samba-tool user list
dns-DOMSLAVE
dns-dommaster
Administrator
Guest
krbtgt
tester
The samba server seems to start anyway but with errors throwing when looking
into the status:
systemctl status samba
? samba.service - Samba AD Daemon
Loaded: loaded (/lib/systemd/system/samba.service; enabled; vendor preset:
enabled)
Active: active (running) since Tue 2022-10-11 07:48:37 CEST; 20min ago
Docs: man:samba(8)
man:samba(7)
man:smb.conf(5)
Main PID: 2426 (samba)
Status: "samba: ready to serve connections..."
Tasks: 56 (limit: 154241)
Memory: 168.4M
CPU: 5.220s
CGroup: /system.slice/samba.service
??2426 samba: root process
??2427 samba: tfork waiter process(2428)
??2428 samba: task[s3fs] pre-fork master
??2429 samba: tfork waiter process(2431)
??2430 samba: tfork waiter process(2433)
??2431 samba: task[rpc] pre-fork master
??2432 samba: tfork waiter process(2434)
??2433 /usr/sbin/smbd -D --option=server role check:inhibit=yes
--foreground
??2434 samba: task[nbt] pre-fork master
??2435 samba: tfork waiter process(2437)
??2436 samba: tfork waiter process(2438)
??2437 samba: task[wrepl] pre-fork master
??2438 samba: task[rpc] pre-forked worker(0)
??2439 samba: tfork waiter process(2441)
??2440 samba: tfork waiter process(2442)
??2441 samba: task[ldap] pre-fork master
??2442 samba: task[rpc] pre-forked worker(1)
??2443 samba: tfork waiter process(2445)
??2444 samba: tfork waiter process(2446)
??2445 samba: task[cldap] pre-fork master
??2446 samba: task[rpc] pre-forked worker(2)
??2447 samba: tfork waiter process(2449)
??2448 samba: tfork waiter process(2450)
??2449 samba: task[kdc] pre-fork master
??2450 samba: task[rpc] pre-forked worker(3)
??2451 samba: tfork waiter process(2453)
??2452 samba: tfork waiter process(2454)
??2453 samba: task[drepl] pre-fork master
??2454 samba: task[kdc] pre-forked worker(0)
??2455 samba: tfork waiter process(2457)
??2456 samba: tfork waiter process(2458)
??2457 samba: task[winbindd] pre-fork master
??2458 samba: task[kdc] pre-forked worker(1)
??2459 samba: tfork waiter process(2462)
??2460 samba: tfork waiter process(2463)
??2461 samba: tfork waiter process(2465)
??2462 samba: task[ntp_signd] pre-fork master
??2463 /usr/sbin/winbindd -D --option=server role check:inhibit=yes
--foreground
??2464 samba: tfork waiter process(2466)
??2465 samba: task[kdc] pre-forked worker(2)
??2466 samba: task[kcc] pre-fork master
??2467 samba: tfork waiter process(2469)
??2468 samba: tfork waiter process(2470)
??2469 samba: task[kdc] pre-forked worker(3)
??2470 samba: task[dnsupdate] pre-fork master
??2476 samba: tfork waiter process(2477)
??2477 samba: task[ldap] pre-forked worker(0)
??2478 samba: tfork waiter process(2479)
??2479 samba: task[ldap] pre-forked worker(1)
??2480 samba: tfork waiter process(2481)
??2481 samba: task[ldap] pre-forked worker(2)
??2482 samba: tfork waiter process(2483)
??2483 samba: task[ldap] pre-forked worker(3)
??2485 /usr/sbin/smbd -D --option=server role check:inhibit=yes
--foreground
??2486 /usr/sbin/smbd -D --option=server role check:inhibit=yes
--foreground
??2487 winbindd: domain child [TLK]
Okt 11 08:08:53 dommaster samba[2466]: [2022/10/11 08:08:53.553116, 0]
../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler)
Okt 11 08:08:53 dommaster samba[2466]: /usr/sbin/samba_kcc: #39
/usr/bin/python3(Py_RunMain+0x2b3) [0x60d4e3]
Okt 11 08:08:53 dommaster samba[2466]: [2022/10/11 08:08:53.553147, 0]
../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler)
Okt 11 08:08:53 dommaster samba[2466]: /usr/sbin/samba_kcc: #40
/usr/bin/python3(Py_BytesMain+0x29) [0x5ea6e9]
Okt 11 08:08:53 dommaster samba[2466]: [2022/10/11 08:08:53.553170, 0]
../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler)
Okt 11 08:08:53 dommaster samba[2466]: /usr/sbin/samba_kcc: #41
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7fce>
Okt 11 08:08:53 dommaster samba[2466]: [2022/10/11 08:08:53.553194, 0]
../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler)
Okt 11 08:08:53 dommaster samba[2466]: /usr/sbin/samba_kcc: #42
/usr/bin/python3(_start+0x2a) [0x5ea5ea]
Okt 11 08:08:53 dommaster samba[2466]: [2022/10/11 08:08:53.557001, 0]
../../source4/dsdb/kcc/kcc_periodic.c:790(samba_kcc_done)
Okt 11 08:08:53 dommaster samba[2466]:
../../source4/dsdb/kcc/kcc_periodic.c:790: Failed samba_kcc -
NT_STATUS_UNSUCCESSFUL
lines 57-79/79 (END)
Can you please look deeper in it?
Greetings
Daniel
Von: Andrew Bartlett [mailto:abartlet at samba.org]
Gesendet: Montag, 3. Oktober 2022 23:36
An: mueller at tropenklinik.de; samba at lists.samba.org
Betreff: Re: [Samba] Error domain level command , modul version mismatch
It isn't clear to me exactly where the mixup is happening, but Rowland is
exactly on the money, this is an issue with conflicting Samba components.
Check you are not mixing a Samba-provided ldb installation with a system
provided one, for example, and that there are not other stray Samba components
around.
Andrew
On Fri, 2022-09-30 at 13:34 +0200, Mueller via samba wrote:
I have checked all files in all directories. They are all new with the
timestamp of the update no old files left!
samba-tool -V
4.17.0
smbstatus -V
Version 4.17.0
samba_dnsupdate -V
4.17.0
Could it be it is going with the wrong ldb version? Any idea how I can
test that?
Greetings
Daniel
EDV Daniel M?ller
Leitung EDV
Tropenklinik Paul-Lechler-Krankenhaus
Paul-Lechler-Str. 24
72076 T?bingen
Tel.: 07071/206-463, Fax: 07071/206-499
eMail:
mueller at tropenklinik.de
Internet:
www.tropenklinik.de
-----Urspr?ngliche Nachricht-----
Von: Rowland Penny via samba [mailto:
samba at lists.samba.org
]
Gesendet: Freitag, 30. September 2022 13:14
An:
samba at lists.samba.org
Cc: Rowland Penny <
rpenny at samba.org
>
Betreff: Re: [Samba] Error domain level command , modul version mismatch
On 30/09/2022 11:54, Mueller wrote:
Hello,
my OS: Debian 11 x64.
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
I updated from samba 4.16.4 straight to 4.17.0. Both Version I
compiled from source.
I think what is happening here is that by updating samba in the way you
have, there are old parts of the original Samba install left. I would
suggest that if you are going to upgrade in this way, you compile Samba on a
new Computer (or VM) and then join this as a new DC and then, once the new
DC is known to be working correctly, demote the old DC. that way you know
there is no old components left behind.
Rowland
--
To unsubscribe from this list go to the following URL and read the
instructions:
https://lists.samba.org/mailman/options/samba
--
Andrew Bartlett (he/him) https://samba.org/~abartlet/
Samba Team Member (since 2001) https://samba.org
Samba Team Lead, Catalyst IT https://catalyst.net.nz/services/samba
Samba Development and Support, Catalyst IT - Expert Open Source
Solutions