similar to: Filesystem does not support posix ACLs

Hi, I am trying to get some integration tests running in CI with a software uses samba4 AD for authentication. So basically I would like spin up a build and provision a samba4 AD with some test users and groups non-interactively and test commits and pull requests against the AD. On 11/14/19 8:16 AM, Andrew Bartlett wrote: > On Thu, 2019-11-14 at 06:19 +0000, Ghassan Elrayah via samba wrote:

On Thu, 2019-11-14 at 06:19 +0000, Ghassan Elrayah via samba wrote: > 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: Can you explain a bit more about what you are doing with CircleCI? This will help me understand how best to advise you. >

Thanks a lot for the reference how to make the regtest. One last question please, if understand this correctly, the --use-ntvfs isnot available by default when installing the Debian package, so I need to compile samba with --with-ntvfs-fileserver to make the option available? On 11/14/19 8:52 AM, Andrew Bartlett wrote: > On Thu, 2019-11-14 at 07:30 +0000, Ghassan Elrayah wrote: >> Hi,

Hi again, it seems that the configure option (--with-ntvfs-fileserer, --enable-developer) are not available on samba-4.11.2. I get the following error: + --enable-developer --with-ntvfs-fileserver --sysconfdir=/etc/samba/ --mandir=/usr/share/man/ --sbindir=/usr/sbin/ --bindir=/usr/bin/ --without-systemd --with-statedir=/var/lib/samba --with-cachedir=/var/cache/samba

Yeah, you will need to do that. Even for the supported default fileserver, the module we use in testing 'vfs_fake_acls' is only provided to developers, so that will be the easiest route to start. When we eventually remove it, come back and we will find a way to keep this working for you. Andrew Bartlett On Thu, 2019-11-14 at 07:59 +0000, Ghassan Elrayah via samba wrote: > Thanks a

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:

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 > > <samba at lists.samba.org > > > wrote: > > > > > On Thu, 1 Sep 2016 14:12:21 +0100 > > >

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

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 there, I am trying to upgrade my old Samba3 (with LDAP backend) to Samba 4. I am doing this on a test VM for now as a proof of concept. When running this command: /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/home/administrator/samba3/ --use-xattrs=yes --realm=internal.com /home/administrator/samba3/smb.conf I get this: Reading smb.conf Provisioning Exporting account

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 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

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

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

Hello, I got a problem with adding an new dc to a domain. when I try to join I get the following: [root at dc-12 etc]# samba-tool domain join obel.lan DC -Uadministrator --server=dc-11 Password for [OBEL\administrator]: workgroup is OBEL realm is obel.lan Adding CN=DC-12,OU=Domain Controllers,DC=obel,DC=lan Adding

I am trying to install samba 4.5.1 from source, as a domain controller only, under Ubuntu 16.04, with ZFS filesystem (actually inside an lxd container with ZFS backing). Out-of-the-box, samba-tool domain provision does not like the filesystem: ERROR(<class 'samba.provision.ProvisioningError'>): Provision failed - ProvisioningError: Your filesystem or build does not support posix

Dear samab developer, Im getting the below error while using samba-tool domain provision and others like dbcheck and time, [root at emad-srv1 bin]# ./samba-tool domain provision --use-rfc2307 --interactive Realm: EMAD.HC Domain [EMAD]: Server Role (dc, member, standalone) [dc]: DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE) [SAMBA_INTERNAL]: BIND9_DLZ Administrator password:

Hi everybody. One month ago me migrated from samba 3.6 classic domain to samba4. After solving some minor problems, we have found ourselves with a ACL corruption and we don't know how to deal with this. When accesing to our sysvol shared (for example, \\domain.local\sysvol) from both Samba or Windows clients, we are refused to connect. Domain=[VECTORSF] OS=[Unix] Server=[Samba 4.1.4]

Hello! I am not able to joing new Samba DC to existing domain: Linux side: OS: Centos 7 Samba version: 4.9.8 (Tranquil repo) Hostname: adserver9 Windows side: OS: Windows Server 2016 Domain/forrest level: Windows Server 2008 R2 Hostname: adserver8 Domain: spcr.local I am following this guide: https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory I am getting this

I tried joining the same AD before and succeeded, however after upgrading to Debian Buster and installing AD Certificate Services on the Windows DC my join does not work anymore: samba-tool domain join samdom.example.com DC -U?SAMDOM\adadmin? ?site=?KA-H9? fails during the ldap part with: Join failed - cleaning up Failed to bind - LDAP error 49 LDAP_INVALID_CREDENTIALS - <8009030C: LdapErr: