similar to: Samba4: no --use-ntvfs option on samba-tool ntacl sysvolcheck

I just realize that i can't run a "samba-tool ntacl sysvolcheck" on my DC's (4.7.6): ldb: unable to open modules directory '/usr/lib/x86_64-linux-gnu/ldb/modules/ldb' - Too many open files ldb: unable to open modules directory '/usr/lib/x86_64-linux-gnu/samba/ldb' - Too many open files ..... >From memory, it was just fine on samba 4.6 If I check system

Hi all, We're seeing the following: root at dc3:~# samba-tool ntacl sysvolcheck rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[netlogon]" Processing section "[sysvol]" ERROR(<type 'exceptions.TypeError'>): uncaught exception - (61, 'No data available') File

Hi I'm with this problem? Version: Samba 4.3 (4.2 upgrade) S.O .: Ubuntu 4.14 samba-tool ntacl sysvolreset open: error=2 (No such file or directory) ERROR(runtime): uncaught exception - (-1073741823, 'Undetermined error') File "/opt/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run return self.run(*args, **kwargs) File

That's not a problem its just a ACL provisioning message as you can see the result was "DAG:DAD:PAI" but expected was "O:DAG:DAD:PAR" that's "normal" ;-) just ignore it or do a "samba-tool ntacl sysvolreset" Am 19.10.23 um 17:27 schrieb bd730c5053df9efb via samba: > Hi! > > I executed the command "samba-tool ntacl sysvolcheck"

Samba 4.4.2 I was doing some maintenance work and I noticed that sysvolcheck gave some error. I ran "samba-tool ntacl sysvolreset". Running sysvolcheck again still gives errors. I tried with several sysvol backups and the result is always the same. The affected policies are always "Default Domain Policy" and "Default Domain Controllers Policy". These policies

I get this error when I run samba-tool ntacl sysvolcheck ProvisioningError('%s ACL on GPO directory %s %s does not match expected value %s from GPO object' % (acl_type(direct_db_access), path, fsacl_sddl, acl)) There are two GPO directories. One is the Default Domain Controllers Policy and one is the Default Domain Policy It looks like it's the Default Domain Policy that's

On my small, one DC AD setup, where I just followed the wiki and did not (!) make any other changes except for working on the AD through the RSAT, I ran samba-tool ntacl sysvolcheck and got the following output: --------------------snip-------------------- ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: DB ACL on GPO directory

Hi, after adding a new GPO the ntacl sysvolcheck fails and i want wo repair with ntacl sysvolreset.... biut this fails aslo in the end with: connect_acl_xattr: setting 'inherit acls = true' 'dos filemode = true' and 'force unknown acl user = true' for service sysvol open: error=2 (No such file or directory) ERROR(runtime): uncaught exception - (-1073741823,

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! I executed the command "samba-tool ntacl sysvolcheck" on a DC and I got the following I pasted below. The first DC was provisioned migrating from a samba NT4 PDC with an LDAP backend using the classic upgrade procedure. I haven't detected any problem but I wanted to make sure there isn't any problem I might not be seeing yet. ERROR(<class

> > > Yes, There are three places where permissions are stored on sysvol (4 if you count in AD), the standard Linux permissions 'ugo', POSIX > ACLs as shown by getfacl and an EA (this is where the ACLs are stored when set from Windows). > > Try running 'samba-tool ntacl get /var/lib/samba/sysvol --as-sddl', this should produce something similar to this: >

I run the sysvolreset by without it when I duplicate the gpo (rsync) problems occurs later on windows machines perform the same on the DC that received the copy .... Regards.... Em 16-06-2017 15:08, Rowland Penny via samba escreveu: > Mine looks similar, but I am/was trying to get samba-tool to work > correctly so there are some differences. Did you know that 'Domain >

Hi! Since samba4 rc1 (we update it since beta1) the "./samba-tool ntacl sysvolcheck" command returns the following : ERROR(<type 'exceptions.TypeError'>): uncaught exception - (61, 'No data available') File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 168, in _run return self.run(*args, **kwargs) File

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]

Raspian root at samba01:~# uname -a Linux samba01 4.9.14-v7+ #977 SMP Mon Mar 13 18:25:19 GMT 2017 armv7l GNU/Linux root at samba01:~# cat /etc/debian_version 8.7 root at samba01:~# samba -V Version 4.6.3 root at samba01:~# cat /etc/samba/smb.conf # Global parameters [global] netbios name = SAMBA01 realm = LOCAL.xx.xx workgroup = LAURENZ server role = active

I have a samba DC based on Debian Buster running samba 4.12.2 from Louis' repo. A second DC on Raspbian buster is running samba 4.12.0. I have sysvol replication working using rsync/unison as per the WiKi. I wasn't having any issues until I tried to edit a GPO and found that all the acl settings had disappeared. This may have happened when I upgraded the DCs from 4.11.x to 4.12.x

Hi Andrew and Louis, Found the issue: after rsync-ing the sysvol from our old decommissioned DCs, the sysvolreset/sysvolcheck DO work out. I tried to keep the things simple first, by NOT immediately importing our old sysvol contents, but first check with a default sysvol... I thought that the sysvolreset would just reset whatever is located under samba/sysvol, but I guess that it reads the

Can anyone explain what is happening when I run / usr / local / samba / bin / samba-tool ntacl sysvolcheck it and an error? ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: DB ACL on GPO file /usr/local/samba/var/locks/sysvol/tdsfs01.net/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/USER/Scripts/scripts.ini

Hi, I joined a new samba-4.7 DC to our AD, replicated everything over, then turned off the old DCs, seized fsmo roles, and added two extra 4.7 DCs. Everything above succeeded without warnings, and everything seems to be running very well finally, except for the sysvolcheck / sysvolreset. We're on xfs, and the File System Support checks on the samba wiki page all pass, although at the

I've noticed that the samba-tool ntacl sysvolreset --use-s3fs command does not work on a ZFS filesystem on FreeBSD. It does work if sysvol is moved to a volume that is able to be mounted with the acls flag. I will reference a ticket I started with FreeNAS here: https://bugs.freenas.org/issues/4351 As of version 9.2.1.1 s3fs is now the default using the workaround known for FreeBSD.