similar to: Segmentation fault in samba_upgradedns - Samba 4.4.5

On Thu, 1 Sep 2016 14:12:21 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > Trying to understand why you are getting the segfault, I set up freebsd 11.0rc2 in a VM and then installed samba44, I now know where Gentoo gets its ideas from :) After freebsd built everything in the chain of required packages, it finally built Samba, I did notice two things, one it built

On Fri, 2 Sep 2016 13:03:05 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Fri, 2 Sep 2016 12:41:47 +0100 > Cameron Murdoch via samba <samba at lists.samba.org> wrote: > > > On 2 September 2016 at 12:21, Rowland Penny via samba > > <samba at lists.samba.org > > > wrote: > > > > > On Fri, 2 Sep 2016 11:51:02 +0100

On 2 September 2016 at 13:19, Rowland Penny via samba <samba at lists.samba.org > wrote: > On Fri, 2 Sep 2016 13:03:05 +0100 > Rowland Penny via samba <samba at lists.samba.org> wrote: > > > On Fri, 2 Sep 2016 12:41:47 +0100 > > Cameron Murdoch via samba <samba at lists.samba.org> wrote: > > > > > On 2 September 2016 at 12:21, Rowland Penny

On Fri, 2 Sep 2016 12:41:47 +0100 Cameron Murdoch via samba <samba at lists.samba.org> wrote: > On 2 September 2016 at 12:21, Rowland Penny via samba > <samba at lists.samba.org > > wrote: > > > On Fri, 2 Sep 2016 11:51:02 +0100 > > Cameron Murdoch <cam at macaroon.net> wrote: > > > > > On 2 September 2016 at 09:53, Rowland Penny via samba

I have samba 4.3 running on FreeBSD 10.2 on ZFS and I am unable to create new GPOs, getting "invalid Parameter" response.Log files indicate ACL issues. Domain was provisioned with --use-ntvfs option.Filesystem is mounted with this options:zroot/ROOT/default on / (zfs, local, noatime, nfsv4acls) acl options on zfs are this:zroot/ROOT/default aclmode passthrough inherited from

On 2 September 2016 at 09:53, Rowland Penny via samba <samba at lists.samba.org > wrote: > On Thu, 1 Sep 2016 14:12:21 +0100 > Rowland Penny via samba <samba at lists.samba.org> wrote: > > > > > Trying to understand why you are getting the segfault, I set up freebsd > 11.0rc2 in a VM and then installed samba44, I now know where Gentoo > gets its ideas from

Hi list, I'm attempting my first ever install of Samba4, my requirements are pretty simple: I just need the quickest easiest way to get a standalone server for use as a Windows file server with password aging and password complexity rules. My OS is FreeBSD 10.2 running on ZFS, samba from binary package samba43-4.3.3. I've had a google for some guides and I've been using the

On 1 September 2016 at 13:15, Rowland Penny via samba <samba at lists.samba.org > wrote: > On Thu, 1 Sep 2016 12:24:38 +0100 > Cameron Murdoch via samba <samba at lists.samba.org> wrote: > > > Hi, > > > > I'm having the following issue when trying to switch from > > samba_internal to bind9_dlz. I have been following the procedure here: > >

On 8 September 2016 at 08:17, Rowland Penny via samba <samba at lists.samba.org > wrote: > On Thu, 08 Sep 2016 12:58:18 +1200 > Andrew Bartlett <abartlet at samba.org> wrote: > > > On Fri, 2016-09-02 at 13:19 +0100, Rowland Penny via samba wrote: > > > > > > > > > I have now found out why you had to provision with samba43, > > > the

On Tue, February 7, 2017 14:29, Alnis Morics wrote: > May I ask an off-topic question? > > James, does saying "samba43" mean you installed this FreeBSD port or > package? Which is known to crash during provisioning as DC. Did you > find the solution to that issue? > Samba43 was installed on FreeBSD-10.3 as a binary package using the pkg utility. Other than ignorance I

On Thu, 9 Feb 2017 20:17:11 -0500 "James B. Byrne" <byrnejb at harte-lyne.ca> wrote: > > Does this mean that I have missed a step in provisioning? Or does it > mean there is a defect in the packaging for FreeBSD? > I am wondering if you have actually fully provisioned. I have tried to provision samba44 and, for some reason, it will not run the provision command

On Fri, 2016-09-02 at 13:19 +0100, Rowland Penny via samba wrote: >  > > I have now found out why you had to provision with samba43, > the '--use-ntvfs' option is gone from Samba 4.4.x. I never noticed > because, as I said, I never used it. > This does of course mean that you cannot use the latest versions of > Samba as an AD DC with freebsd unless somehow either

Hi at all, i´am using samba 4.3.4 as "ad", "migrated by classicupgrade" some time ago from an nt4-domain. By trying samba_upgradedns --dns-backend=BIND9_DLZ i get the following error: Traceback (most recent call last): File "/usr/sbin/samba_upgradedns", line 262, in <module> paths, lp.configfile, lp) File

Am Dienstag, 2. Februar 2016, 09:51:03 CET schrieb Rowland penny: > On 01/02/16 22:24, Markus Dellermann wrote: > > Hi at all, > > > > i´am using samba 4.3.4 as "ad", "migrated by classicupgrade" some time ago > > from an nt4-domain. > > > > By trying > > samba_upgradedns --dns-backend=BIND9_DLZ > > > > i get the

Hi, I am trying to create a build on CircleCi with smaba4 AD. It seems the filesytem doesn't support ACL's, which s3fs requires. I get the folowing error: ?ERROR(<class 'samba.provision.ProvisioningError'>): Provision failed - ProvisioningError: Your filesystem or build does not support posix ACLs, which s3fs requires.? Try the mounting the filesystem with the

Hello! I've just built my first samba4 (4.0.5) on an OpenIndiana machine without any problems. But when it comes to the provision step the problems begin. Everything is fine, if I call samba-tool with the --use-ntvfs option. But I want to use samba4 with s3fs because of the support for newer SMB protocol versions. But when I call samba-tool without --use-ntvfs option I got the following:

Hi Everybody, I'm stumped. I'm pretty sure I've tried everything to get this to work. I'm trying to join my CentOS 6 server to my Server 2008 AD Domain. I'm using SerNet's samba4 packages: [root at files ~]# samba -V Version 4.1.4-SerNet-RedHat-7.el6 I've done the xattr and acl tests and they all come out just fine. So I don't think it has to do with ACLs

Hi , We migrated to AD account in a Ubuntu 16.04 (Samba 4.3.11)and came across issues with user shares. Some of the users were able to access the shares and some were not. The server in question has both AD and File and we followed the samba wiki to enable the Windows ACL To migrate , we ran the following samba-tool domain classicupgrade --dbdir=/var/lib/samba.PDC/dbdir --realm=lin.GROUP

On 02/02/16 11:26, Markus Dellermann wrote: > Am Dienstag, 2. Februar 2016, 09:51:03 CET schrieb Rowland penny: >> On 01/02/16 22:24, Markus Dellermann wrote: >>> Hi at all, >>> >>> i´am using samba 4.3.4 as "ad", "migrated by classicupgrade" some time ago >>> from an nt4-domain. >>> >>> By trying >>>

On 2016-01-15, ROWLAND PENNY wrote: > Try running 'samba -b' this will show you where the AD DC expects to > find things, you should be able to work out from there what needs > changing on your system. Ok thanks. I wasn't sure which of the listed directories was important. I ran samba-tool with debug 9 and I think the issue is where it tries to create the sysvol volume,