similar to: 'set_simple_acl' referenced before assignment in classicupgrade

Rowland Penny via samba <samba at lists.samba.org> writes: > On Thu, 22 Mar 2018 10:50:35 +0700 > Olivier via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> I am progressing slowly with the migration from Samba3 to Samba4. >> >> I have escaped the bug 13060, now I get to: >> >> Adding groups >> Importing groups

I'm trying to upgrade from samba3 -> 4. I ran this command: WORKDIR=/usr/local/mobius /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=$WORKDIR/var --use-xattrs=yes --realm=infinityhealthcare.com $WORKDIR/smb.conf but it failed with the error given in this email's subject. What does it mean, and how do I fix it? This is just another is a growing line of errors that

ClassicUpgrade of my samba3 data to samba4 fails, with this error: ERROR(<class 'passdb.error'>): uncaught exception - Unable to get id for sid Full log of the classicupgrade is at the end of this email. Project member on this list, Andrew Barlett, wrote that the issue is probably that my Samba 3 passdb was passable in an NT 4 DC mode, but is actually 'invalid' :

Hi, I'm practising to do a classicupgrade of my samba3 domain. When I run the upgrade, I get this error : unpack_nt_owners: owner sid mapped to uid 0 idmapping sid_to_xid failed for id[0]=S-1-5-32-544: NT_STATUS_NONE_MAPPED unpack_nt_owners: unable to validate group sid. set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_OWNER. ERROR(runtime): uncaught exception - (-1073741734,

On Thu, 22 Mar 2018 10:50:35 +0700 Olivier via samba <samba at lists.samba.org> wrote: > Hi, > > I am progressing slowly with the migration from Samba3 to Samba4. > > I have escaped the bug 13060, now I get to: > > Adding groups > Importing groups > Group already exists > sid=S-1-5-21-1360262076-8766554542-0991298654-513, groupname=Unix > Group Users

Hi, When trying to upgrade from Samba 3.6.25 on FreeBSD 10.3-RELEASE-p17 to Samba 4.7.6 on FreeBSD 11.1-RELEASE-p6, I receive an error: # samba-tool domain classicupgrade --dbdir=/usr/local/etc/samba3/ --realm=samdom.example.com --dns-backend=BIND9_DLZ /usr/local/etc/samba3/smb.conf [...] Committing 'add users' transaction to disk Adding users to groups Committing 'add users to

On Wed, 04 Apr 2018 15:13:09 +0700 Olivier via samba <samba at lists.samba.org> wrote: > Hi, > > When trying to upgrade from Samba 3.6.25 on FreeBSD 10.3-RELEASE-p17 > to Samba 4.7.6 on FreeBSD 11.1-RELEASE-p6, I receive an error: > > # samba-tool domain classicupgrade --dbdir=/usr/local/etc/samba3/ > --realm=samdom.example.com --dns-backend=BIND9_DLZ >

Hi, I have a problem during the classicupgrade. The problem was discussed in march on this list, but there seems to be nosolution. Can anyone help? ... Setting password for administrator Administrator password has been set to password of user 'root' idmapping sid_to_xid failed for id[0]=S-1-5-32-544: NT_STATUS_NONE_MAPPED set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_OWNER.

Hi All, Attempting to do a classicupgrade and getting this error: *Adding groups* *Importing groups* *Committing 'add groups' transaction to disk* *Adding users* *Importing users* *Adding users to groups* *Committing 'add users to groups' transaction to disk* *ERROR(<type 'exceptions.ValueError'>): uncaught exception - zero length field name in format* * File

On Sun, 16 Sep 2018 10:51:25 -0400 Bill Baird via samba <samba at lists.samba.org> wrote: > I ran the same thing with 4.8.5 and it work without any issues: > > Adding groups > Importing groups > Committing 'add groups' transaction to disk > Adding users > Importing users > Committing 'add users' transaction to disk > Adding users to groups >

Hi Denis, Thanks for your advices. I have in mind about your kerberos problem in a large environment but i was thinking about problem occuring at 20 and more DCC's So last night, i modified all my krb5.conf (DC and file server) as you suggest but problem persist. root at dc111:~# samba-tool domain join pr.educationetformation.fr DC -U administrator --realm=PR.EDUCATIONETFORMATION.FR -W PR

Hello, i try to upgrade a NT4-PDC to AD. OS: Debian 10.1 Samba: 4.9.5-Debian read https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade) scp -r /var/lib/samba/private/ /var/lib/samba/samba3tdb/ scp /etc/samba/smb.conf /var/lib/samba/samba3tdb/ samba-tool domain classicupgrade --dbdir=/var/lib/samba/samba3tdb/ --realm=samdom.example.com

Guys, I'm facing this problem too: https://lists.samba.org/archive/samba/2013-March/172230.html I have two Samba4 AC DC, in both located in my office, dual-stacked, working like a charm. Now, I need to deploy a third DC, located within Amazon EC2, which does NOT have IPv6. But, samba-tool fails to join. How can I workaround this, without enabling a tunneled IPv6 within my EC2 ?

Hi, i have a problem upgrading an old samba 3.5.x to 4.0.9. The upgrade ends with: Setting password for administrator Administrator password has been set to password of user 'root' set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_OWNER. ERROR(runtime): uncaught exception - (-1073741734, 'NT_STATUS_INVALID_OWNER') File

I'm trying to upgrade to AD from a Samba 4 PDC with openLDAP (on Debian 8). I'm stuck at this very unhelpful error: # samba-tool domain classicupgrade --dbdir=/usr/local/samba.PDC/dbdir/ --use-xattrs=yes --realm=ad.mydomain.tld --dns-backend=SAMBA_INTERNAL --option="interfaces=lo eth2" --option="bind interfaces only=yes" /etc/samba/smb.conf.PDC

Hi list, I just tried to add a second DC to an existing Samba4 domain using samba-tool (both hosts run latest samba4 git version). But the join failed, complaining about being unable to find a writeable DC: root at elektron:~# /opt/samba4/bin/samba-tool domain join linex.r00t.la DC Finding a writeable DC for domain 'linex.r00t.la' ERROR(exception): uncaught exception - Failed to find a

other errors that I have when I try to join BDC with samba 4 is the follow Try the mounting the filesystem with the 'acl' option.") Deleted CN=DANTES,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=eccmg,DC=cupet,DC=cu ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: Your filesystem or build does not

I cannot join two new VMs to my domain, I receive the following error on both machines: twerks at cbadc03:~$ kinit Administrator Password for Administrator at CB.CLIFFBELLS.COM: itwerks at cbadc03:~$ klist -e Ticket cache: FILE:/tmp/krb5cc_1000 Default principal: Administrator at CB.CLIFFBELLS.COM Valid starting Expires Service principal 03/21/2016 00:19:56 03/21/2016

I have a new server running CentOS 6.4 x64, which will serve as our new Samba4 server. It is set up in a test environment, and I've copied over the tdb files and the smb.conf file from our samba3 server (Same OS and version). I'm trying to do an in-place upgrade on the copied files, but keep hitting an assert / uncaught exception during the upgrade: # /usr/local/samba/bin/samba-tool

Hello, I inherited an Active directory in Windows in Spanish, after a lot of work I was able to do the first synchronization to a DC in Samba. Now I am at the stage that I want to remove Windows, but previously I want to remove Windows. I am trying to add another DC in Samba to advance and I am presented with the following problem. I feel lost with these errors. root at DC01:~# samba-tool fsmo