Displaying 20 results from an estimated 2000 matches similar to: "classicupgrade fails on rc6, worked on rc5"
2012 Aug 23
1
Another problem with samba4 classicupgrade
Hello
I've used the following command :
/usr/local/samba/bin/samba-tool domain classicupgrade
--dbdir=/root/samba3/ --realm=sc.isc84.org /root/samba3/smb.conf
And the following error :
...
Importing Account policy
Importing idmap database
Cannot open idmap database, Ignoring: [Errno 2] No such file or directory
Exporting posix attributes
*ERROR(<type
2013 Jan 03
1
samba-tool domain classicupgrade with LDAP backend
Hi
I am testing the migration from our actual Samba domain, based on Samba
3.3.8 and LDAP (389DS) to Samba 4. I have followed the Samba4 Howto, and I
have successfully compiled it. Now I am running the classicupgrade command,
but I am getting some errors.
First of them is that the script is ignoring the "ldap group suffix"
parameter in smb.conf, and is always searching in the
2015 Jun 04
1
error when samba-tool domain classicupgrade
When you try to upgrade on a test stand, an error occurs.
I do not understand that you need to add ldap, or improve migration script?
Before that I tried to version 4.1.7, but the error was the sam
root at dc1:~/smb_old# samba --version
Version 4.2.2-SerNet-Ubuntu-7.trusty
I also modified the file
--- ./upgrade.py 2014-10-01 00:00:00.000000000 +0600
+++
2013 Aug 16
1
WARNING: Module [samba_secrets] not found (samba 4.0.8, classicupgrade)
Samba 4.0.8, from the tarball, compiled with
./configure
make
sudo make install
# /usr/local/samba/sbin/samba -b
Samba version: 4.0.8
Build environment:
Build host: Linux template.wetron.local 3.8.13.4-server-1.mga3 #1
SMP Thu Jul 4 14:04:54 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Paths:
BINDIR: /usr/local/samba/bin
SBINDIR: /usr/local/samba/sbin
CONFIGFILE:
2016 Jun 29
4
Classicupgrade of 4.1.17 error: "list index out of range"
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
2016 Jun 29
0
Classicupgrade of 4.1.17 error: "list index out of range"
Hi MI,
> 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
2013 Feb 11
2
Classicupgrade not work
I'm trying to convert my samba3 domain to samba4 AD with samba-tool,
but i'm getting an error and i can' t find anything about it on
google.
I've enabled the log level 4 on smb.conf and here's what i got:
Home server: PANDORA
init_sam_from_ldap: Entry found for user: DIRET-ESTAG$
Home server: PANDORA
init_sam_from_ldap: Entry found for user: dsegato
Home server: PANDORA
2018 Mar 22
4
'set_simple_acl' referenced before assignment in classicupgrade
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 existing_groupname=Domain Users, Ignoring.
Committing 'add groups' transaction to disk
Adding users
Importing users
Committing 'add
2018 Sep 16
3
ClassicUpgrade: ERROR(<type 'exceptions.ValueError'>): uncaught exception - zero length field name in format
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
2015 May 21
2
Import idmap database error on classicupgrade process
I copied all the database files of samba3 as is mentioned in the wiki - The
classicupgrade process
<https://wiki.samba.org/index.php/Samba_Classic_Upgrade_(NT4-style_domain_to_AD)#The_classicupgrade_process>
But if the winbindd_idmap.tdb file is in the folder, the errors occur. See
below:
Importing idmap database
> ERROR(assert): uncaught exception
> File
2018 Mar 26
1
'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
2012 Nov 16
1
Samba4 - Wins error running samba-tool classicupgrade
Hello:
First, sorry for my English.
I'm testing samba4 rc5. I have compiled and installed samba4 and now I'm
trying to simulate an upgrade from my samba3 site to my samba4 test
installation. I have setup a isolated network and I have replicated
server and clients, copied my samba3 ldap contents and tdb files.
But, when I run samba-tool classicupgrade following to the docs,
2018 Sep 16
3
ClassicUpgrade: ERROR(<type 'exceptions.ValueError'>): uncaught exception - zero length field name in format
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
>
2013 Jul 08
1
samba4 - error during classicupgrade
Hi all,
I have a problem during classic-upgrade :
Importing groups
Group already exists sid=S-1-5-21-4023731279-819928261-1073345436-512,
groupname=Domain Admins existing_groupname=Domain Admins, Ignoring.
Group already exists sid=S-1-5-21-4023731279-819928261-1073345436-514,
groupname=Domain Guest existing_groupname=Domain Guests, Ignoring.
Group already exists
2013 Jul 29
1
Samba4 - Classicupgrade - pdb_init_ldapsam: WARNING: Could not get domain info, nor add one to the domain
Hi Team,
*I'm migrating to samba4 (samba 4.0.7) and doing "Upgrading In Place"
**and running classicupgrade; *I have installed openldap-devel...as im
migrating database from ldap.* *
*while doing this am getting the following error message:*
# /usr/local/samba/bin/samba-tool domain classicupgrade
--dbdir=/samba-backup/ --use-xattrs=yes
--realm=mydomain.com/samba-backup/smb.conf
2013 Dec 17
1
Samba classicupgrade problem
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,
2014 Jun 11
1
Issues with classicupgrade LDAP
Hi there,
I'm attempting a classicupgrade from Samba3 to Samba4 with an LDAP
backend and encountering this error:
dpadmin at samba4-dev0:~$ samba-tool domain classicupgrade
--dbdir=/var/lib/samba --use-xattrs=yes --realm=ad.digipen.edu
/home/dpadmin/smb.conf 2>&1 | tee SambaMigration10.log
<snip>
init_sam_from_ldap: Entry found for user: steven.redacted
init_sam_from_ldap:
2015 May 21
2
Import idmap database error on classicupgrade process
You're right, man! Sorry! My mistake!
I put that file because I read in somewhere about the persistent and
temporary files regarding .tdb files. The winbindd_idamp.tbm was on that
list, and I think that's why I left it in the folder. :D
Another doubt. For the provisioning starts, I had to comment out the line
referring to the ldap backend in the smb.conf of samba3.
# passdb backend =
2013 Aug 30
1
Error on classicupgrade - Unable to get id for sid
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
2015 Aug 11
3
Issue with computer accounts with classicupgrade
I have an old Centos5/Samba3.5 domain with LDAP backend that I am
attempting to migrate to the latest Samba 4.2 on Centos 7.1. Samba in
both cases has been installed using Sernet packages.
I had successfully run the classicupgrade process, but in subsequent
testing found that in the 3.5 domain all the computer accounts have the
posixAccount class and therefore have a uidNumber.