similar to: ldbsearch fails due to LDB_MODULES_PATH not set, is it critical for ADDC operation?

I suggest he runs : rpm -q samba samba-* lib?db* And post that, looks to me he is missing the samba-dsdb-modules and maybe samba-vfs-modules also. But i dont know much about Fedora.. Greetz. Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland Penny via samba > Verzonden: donderdag 28 september 2017 9:59 > Aan:

Hi, The following problem: [root]#kinit administrator kinit: Cannot contact any KDC for realm 'DC-STATIC.LUUFORPROS.COM' while getting initial credentials A restart of samba.service finally starts krb5kdc: [root]#systemctrl restart samba [root]# ps axf |grep krb 1249 pts/0 S+ 0:00 \_ grep --color=auto krb 1212 ? S 0:00 | \_ /usr/sbin/krb5kdc -n

On Tue, 26 Sep 2017 20:19:03 +0200 Marc Muehlfeld <mmuehlfeld at samba.org> wrote: > Hi, > > As you said: It's Fedora 27 _rawhide_. You should report a bug: > https://bugzilla.redhat.com/ > Please don't forget to attach logs, etc. Ok, I just opened a bug over there. But in the meantime found out that: Systemctl status samba.service shows the following as well:

Hi all, After upgrading my first Samba AD DC from el7.4 to el7.5, I had the pain of being greeted with a non-fonctional Samba. When I used samba-tool, I was greeted with that message: root at dc00 ~]# samba-tool dbcheck ldb: module version mismatch in ../source4/dsdb/samdb/ldb_modules/acl.c : ldb_version=1.2.2 module_version=1.1.29 ldb: failed to initialise module /usr/lib64/samba/ldb/acl.so :

Hi Rowland, Yes, that's right (Thank you). Here is what happened: On the DC's, libldb was this version on el7.4: - libldb-1.1.29-2.el7_4.wing.x86_64 (from Wing's repo). el7.5 brought in a more recent version: - libldb-1.2.2-1.el7.x86_64 - libldb-1.2.2-1.el7.i686 What would be the best course of action here? A) Downgrade el7.5 to libldb-1.1.29-2.el7_4.wing.x86_64? B) rebuild

Sorry for all these replies, i missed this. > Is the upgrade path from samba 4.6 + libldb 1.1 to samba 4.6 + libldb 1.3 No, that wil break your samba!!! Samba 4.6 max 1.1.29 for ldb. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Vincent S. Cojot via samba > Verzonden: woensdag 18 april 2018 14:06 >

Hi, I migrated from my the main domain controller.I use Centos 7 server with tranquilrepository. The destination server is a test enviorement with different domain name but the same system specifications. I can browse the sysvol network share without any problem. If i want to check the sam.ldb file on the test server I got these errors. WARNING:Module [samba_dsdb] not found - do you need to

Hi! Sorry my late answer. I did run the sysvolcheck/reset commands and everything seems fine. On my server I use the following rpm packages, installed from the tranquil.it repository. ldb-tools.x86_64 2.0.10-1.el7?????????????????? @samba_custom libldb.x86_64?????????????????????? 2.0.10-1.el7 @samba_custom libldb-devel.x86_64???????????????? 2.0.10-1.el7 @samba_custom

On Mon, Jul 10, 2017 at 8:02 AM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 10 Jul 2017 06:43:37 -0600 > Jeff Sadowski <jeff.sadowski at gmail.com> wrote: > > > Bind-9.11 is installed. How do you configure it? Does it need anything > > special in the config for samba to build the ...samba.../named.conf > > file that I should be able

In /usr/lib64/python2.7/site-packages/samba/provision/sambadns.py Update: It is failing in create_samdb_copy specifically here: # Copy root, config, schema partitions (and any other if any) # Since samdb is open in the current process, copy them in a child process try: tdb_copy(os.path.join(private_dir, "sam.ldb"), os.path.join(dns_dir,

OK so I don't have a program tdbbackup. Where do I get it? On Mon, Jul 10, 2017 at 10:38 AM, Jeff Sadowski <jeff.sadowski at gmail.com> wrote: > > > On Mon, Jul 10, 2017 at 9:45 AM, Jeff Sadowski <jeff.sadowski at gmail.com> > wrote: > >> In /usr/lib64/python2.7/site-packages/samba/provision/sambadns.py >> >> Update: It is failing in

Hi, In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, link on the interface becomes ready several seconds after 'ifup' is executed, which for some buggy images like cirros may slow down boot process for up to 1 minute [2]. If we switch from e1000 to virtio, the link is brought up and ready almost immediately. For the record, I am using the following versions: - L0

On Mon, Oct 3, 2016 at 12:10 PM, Sketch <smblist at rednsx.org> wrote: > > I would assume they would work if you built Samba against them so that > it's ldb modules were built for the same version. But that seems like a > lot of work when you can just use the CentOS ldb-tools package. > Well the ldb-tools package from COS doesn't work, as we've discussed

On Thu, Nov 23, 2017 at 4:05 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Thu, Nov 23, 2017 at 03:00:45PM +0200, Yaniv Kaul wrote: > > On Thu, Nov 23, 2017 at 10:57 AM, Richard W.M. Jones <rjones@redhat.com> > > wrote: > > > > > On Tue, Nov 21, 2017 at 11:43:54PM +0200, Yaniv Kaul wrote: > > > > Since I upgrading to FC27, I

There are two ubuntu 16.04 samba 4.5 servers. Ubuntu ADDC and a Member (ubuntu-dm1) >From Member "wbinfo -u" shows shows users of ADDC >From Member "net ads join -U administrator" was successfull with no errors. The dns A record was added in ADDC. But getent passwd <user> shows no results. DMember's /etc/nsswitch.conf passwd: compat winbind group:

Context: The baremetal host previously had QEMU 2.11. But I manually downgraded the QEMU version (via `dnf downgrade qemu-system-x86`); now it is at 2.10: $ rpm -q qemu-system-x86 qemu-system-x86-2.10.2-1.fc27.x86_64 The guest is offline. Let's see (in a couple of ways) what machine type it has while it is dormant: # virsh dumpxml cirros | grep -i machine= <type

Is using ADUC from a windows machine a complete substitute of what the wiki below explains? https://wiki.samba.org/index.php/LDB#ldbmodify Just curiuos because it seems beyond me at the moment to dig into it. Regards

Hi, just a short update on this issue: By using strace and having a look at the source code, I found the reason for the named error: Accessing samba database via ldapi requires the use of ildap.so (samba ldb module, which is not located in "standard ldb modules path"). Just setting LDB_MODULES_PATH to the directory containing it makes named start: export

client: samba-client-4.7.4-0.fc27.x86_64 client: samba-client-4.6.5-0.fc26.x86_64 server: samba-4.7.3-3.fc27.x86_64 Reproduce steps: [chris at f27h ~]$ smbclient //f27s.local/scratch/ Enter SAMBA\chris's password: Try "help" to get a list of possible commands. smb: \> cd noperms smb: \noperms\> ls . D 0 Wed Jan 3 12:00:27 2018

I have been running experiments and I found an interesting multiple representations of never expiring accounts. I see when I create an account using the ADUC in windows 10 pro on samba-dc-4.7.5-2.fc27 when I use ldapsearch to get accountExpires I get 9223372036854775807 if I set the account to expire I get the expected value for that date. Here is the strange part when I set the account back to