Your message dated Wed, 27 Apr 2022 16:39:33 +0300
with message-id <b2a1956a-cb55-bf7a-09a2-cc3d272d5...@msgid.tls.msk.ru>
and subject line Re: Bug#886333: samba: cannot provision a domain:
ldb_init_module() complains about gpgme_check_version(1.9.0)
has caused the Debian Bug report #886333,
regarding samba: cannot provision a domain: ldb_init_module() complains about
gpgme_check_version(1.9.0)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
886333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.7.3+dfsg-1
Severity: normal
When running "samba-tool domain provision" I get:
# samba-tool domain provision
Realm [HOME.WURTEL.NET]: WURTEL.NET
Domain [WURTEL]:
Server Role (dc, member, standalone) [dc]:
DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE) [SAMBA_INTERNAL]:
DNS forwarder IP address (write 'none' to disable forwarding) [172.18.0.2]:
Administrator password:
Retype password:
Looking up IPv4 addresses
More than one IPv4 address found. Using 172.18.1.11
Looking up IPv6 addresses
More than one IPv6 address found. Using fd2c:2cdd:72b1:0:62e3:27ff:fe05:eec6
ldb_init_module() in ../source4/dsdb/samdb/ldb_modules/password_hash.c
version[1.2.2]: gpgme_check_version(1.9.0) not available,
gpgme_check_version(NULL) => '1.8.0'
ldb: failed to initialise module
/usr/lib/x86_64-linux-gnu/ldb/modules/ldb/samba/password_hash.so : Unavailable
ldb: failed to initialise module
/usr/lib/x86_64-linux-gnu/ldb/modules/ldb/samba : Unavailable
ERROR(<type 'exceptions.MemoryError'>): uncaught exception -
File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 176,
in _run
return self.run(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/samba/netcmd/domain.py", line 474, in
run
nosync=ldap_backend_nosync, ldap_dryrun_mode=ldap_dryrun_mode)
File "/usr/lib/python2.7/dist-packages/samba/provision/__init__.py", line
2080, in provision
schemadn=names.schemadn)
File "/usr/lib/python2.7/dist-packages/samba/schema.py", line 82, in __init__
self.ldb = SamDB(global_schema=False, am_rodc=False)
As this is the first time I'm trying this, it may well be that I've missed
something essential; OTOH I'd expect that when installing from Debian
packages that any details are already taken care of.
Thanks,
Paul
-- Package-specific info:
* /etc/samba/smb.conf present, and attached
* /etc/samba/dhcp.conf present, and attached
-- System Information:
Debian Release: buster/sid
APT prefers oldoldstable
APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.11.3-wurtel-ws (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
Versions of packages samba depends on:
ii adduser 3.115
ii dpkg 1.18.24
ii libattr1 1:2.4.47-2+b2
ii libbsd0 0.8.6-2
ii libc6 2.24-17
ii libldb1 2:1.2.2-2
ii libpam-modules 1.1.8-3.6
ii libpam-runtime 1.1.8-3.6
ii libpopt0 1.16-10+b2
ii libpython2.7 2.7.13-2
ii libtalloc2 2.1.8-1
ii libtdb1 1.3.11-2
ii libtevent0 0.9.31-1
ii lsb-base 9.20161125
ii procps 2:3.3.12-3
ii python 2.7.13-2
ii python-dnspython 1.15.0-1
ii python-samba 2:4.7.3+dfsg-1
ii python2.7 2.7.13-2
ii samba-common 2:4.7.3+dfsg-1
ii samba-common-bin 2:4.7.3+dfsg-1
ii samba-libs 2:4.7.3+dfsg-1
ii tdb-tools 1.3.11-2
Versions of packages samba recommends:
ii attr 1:2.4.47-2+b2
ii logrotate 3.11.0-0.1
ii samba-dsdb-modules 2:4.7.3+dfsg-1
ii samba-vfs-modules 2:4.7.3+dfsg-1
Versions of packages samba suggests:
pn bind9 <none>
pn bind9utils 1:9.11.2+dfsg-5
pn ctdb <none>
pn ldb-tools 2:1.2.2-2
ii ntp 1:4.2.8p10+dfsg-3
pn smbldap-tools 0.9.9-1
pn ufw <none>
ii winbind 2:4.7.3+dfsg-1
-- no debconf information
# Global parameters
[global]
netbios name = WURTEL-WS
realm = WURTEL.NET
workgroup = WURTEL
dns forwarder = 172.18.0.2
server role = active directory domain controller
idmap_ldb:use rfc2307 = yes
[netlogon]
path = /var/lib/samba/sysvol/wurtel.net/scripts
read only = No
[sysvol]
path = /var/lib/samba/sysvol
read only = No
dhcp.conf
Description: inode/empty
--- End Message ---
--- Begin Message ---
Version: 2:4.11.0+dfsg-1
This bug has been fixed upstream somewhere in 4.10 series.
The check is still there now (in 4.16, commit
4ae2fb2e7403191296f7c74f3098fbe121f0796a),
I don't think it makes sense now but that's how things are :)
Closing this bugreport now.
Thanks,
/mjt
--- End Message ---