From owner-freebsd-questions@freebsd.org Wed Jun 22 20:40:25 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 305C4AC5A3F for ; Wed, 22 Jun 2016 20:40:25 +0000 (UTC) (envelope-from mail@kseidel.org) Received: from mx2.mailbox.org (mx2.mailbox.org [80.241.60.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.mailbox.org", Issuer "SwissSign Server Silver CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE2D518E9 for ; Wed, 22 Jun 2016 20:40:24 +0000 (UTC) (envelope-from mail@kseidel.org) Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.mailbox.org (Postfix) with ESMTPS id 6A7B042105; Wed, 22 Jun 2016 22:35:03 +0200 (CEST) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by hefe.heinlein-support.de (hefe.heinlein-support.de [91.198.250.172]) (amavisd-new, port 10030) with ESMTP id 2e2D3h4N9Pnd; Wed, 22 Jun 2016 22:35:02 +0200 (CEST) Subject: Re: FreeBSD-10.3p5 - Samba43-4.3.8 To: freebsd-questions@freebsd.org, byrnejb@harte-lyne.ca References: From: Kevin Seidel Message-ID: Date: Wed, 22 Jun 2016 22:34:54 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2016 20:40:25 -0000 Hi James, this bug was already reported (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208837) and is fixed in samba43-4.3.8_1 and samba43-4.3.9. Regards, Kevin On 22/06/16 9:42 PM, James B. Byrne via freebsd-questions wrote: > I am installing Samba43 on a BHyve VM using zfs - both host and guest. > I am using vm-bhyve on the host. When I go to provision a new AD-DC > I see this: > > # samba-tool domain provision --use-ntvfs --realm=ADOMAIN.EXAMPLE.COM > --domain=ADOMAIN --server-role=dc --dns-backend=SAMBA_INTERNAL > --use-rfc2307 > Administrator password will be set randomly! > Looking up IPv4 addresses > . . . > setting up sam.ldb rootDSE marking as synchronized > Fixing provision GUIDs > ERROR(runtime): uncaught exception - pytalloc_reference_ex() called > for object type not based on talloc > File > "/usr/local/lib/python2.7/site-packages/samba/netcmd/__init__.py", > line 175, in _run > return self.run(*args, **kwargs) > File > "/usr/local/lib/python2.7/site-packages/samba/netcmd/domain.py", > line 442, in run > nosync=ldap_backend_nosync, ldap_dryrun_mode=ldap_dryrun_mode) > File > "/usr/local/lib/python2.7/site-packages/samba/provision/__init__.py", > line 2172, in provision > skip_sysvolacl=skip_sysvolacl) > File > "/usr/local/lib/python2.7/site-packages/samba/provision/__init__.py", > line 1864, in provision_fill > attrs=['defaultObjectCategory']) > File "/usr/local/lib/python2.7/site-packages/samba/dbchecker.py", > line 138, in check_database > error_count += self.check_object(object.dn, attrs=attrs) > File "/usr/local/lib/python2.7/site-packages/samba/dbchecker.py", > line 1358, in check_object > normalised = > self.samdb.dsdb_normalise_attributes(self.samdb_schema, attrname, > [val]) > File "/usr/local/lib/python2.7/site-packages/samba/samdb.py", line > 672, in dsdb_normalise_attributes > return dsdb._dsdb_normalise_attributes(ldb, ldap_display_name, > ldif_elements) > > Referring to this message: > https://lists.samba.org/archive/samba-technical/2016-March/112908.html > > I read this : > > >> As far as I'm aware, the only use case for this is that call >> in dbcheck (here called by provision). While undesirable, the >> failure message is clear (to us, and will quickly find this >> thread in google), and is not an abort(), which is what was >> happening in the same area for some versions previously. > > I further read this: > https://lists.samba.org/archive/samba-technical/2016-March/112923.html > >>> >>> Could you apply the attached patches to your samba-4.3.6 >>> and see if they fix the domain provision? >> Provision of domain is OK with talloc-2.16 and samba-4.3.6 with >> these patches. Thanks. > > > This refers to Samba43-4.3.6. It implies that the domain is not > properly provisioned without those patches. The package from ports I > am using is Samba43-4.3.8 and evidently those patches did not make it > into the source tree. > > So questions remain. Do I have a working samba installation or not? > How can I tell? I do not want to get deeply into setting this stuff up > only to find that a critical piece of infrastructure either is missing > or does not work properly, if at all. > > Any help with or insight into this matter gratefully accepted. > > Sincerely, >