similar to: samba4 - error during classicupgrade

How do we check the data from Samba4 that the data from Samba3 successfully migrated? I dunno if it successfully migrated coz got these (last part): [root at gaara LiveData]# /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/srv/LiveData/var_lib_samba/samba --use-xattrs=yes --realm=kazekage.sura.sandbox.local --dns-backend=SAMBA_INTERNAL /srv/smb.conf Once the above files are

I used to upgrade samba3 to samba4 with almost successful with one problem, administrator can't access. As administrator, by default it is the only user account that is given full control over the system. My query is how to change the administrator password? we have one account which can join to the samba 4 AD based on the migrated data but the problem can't change the administrator or

I have tested the patch against 4.3.1 compiled from sources but it does not seem to work. Either I did something wrong while compiling, or the patch dosen't fix the problem. ERROR(<type 'exceptions.ValueError'>): uncaught exception - unable to parse dn string File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run return

On Fri, Mar 18, 2016 at 4:04 PM, Andrew Bartlett <abartlet at samba.org> wrote: > The upgrade code assumes you run on the same host. I realise now that > folks doing an upgrade use that an an opportunity to upgrade hardware, > and keep old systems as fallbacks, so the assumptions cause trouble. > > Make the new host identical in terms of the data needed to upgrade >

Sorry for the long post but attempted this several over the past year with no success but staying on an NT4 domain is no longer viable. Need to get this resolved so hopefully there will be a clue somewhere in this montage. The current PDC is samba-3.6.25 running on Gentoo using tdbsam backend. The new AD will be a Debian LXC container running on Debian Jessie using samba compiled from git

Hallo, I have two news. The first one: the patch probably works. Second: there is another bug. When I encountered the bug again after patching, I have raised debug level and figured out that the problem is with user "guest" - he was in our old domain, however samba-tool probably creates him automatically and then couldn't import him. So, please fix the tool so that it ignores such

Hello, I run Samba 3.6.3. on ubuntu server, whre the domain works fine. Hoever when I try to migrate to Samba 4.1 from sernet distribution, I finish with Classicupgrade on the below error. I know it hase to do with bad group mapping, but I am not able to find the mistake. Please help. root at server:/var/lib/samba# samba-tool domain classicupgrade --dbdir=/var/lib/samba.PDC/dbdir/

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

Rowland penny wrote on 3/18/16 12:58 PM: > On 18/03/16 19:27, Robert Moulton wrote: >> Rowland penny wrote on 3/18/16 11:48 AM: >>> On 18/03/16 18:19, Robert Moulton wrote: >>>> Greetings - On our samba 4 (4.3.3) AD controller I just noticed >>>> something odd. When I run 'samba-tool fsmo show' I get an error: >>>> >>>> #

Hi, I found the source of my problem with set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_OWNER (I hope). The problem is dut to winbind. In my ldap tree, I have uid and gid. Why samba 4 don't use theses informations ? In attached file : output of classic-upgrade (debug level 5) I don't want to use winbind. I just want to use pam_ldap or nslcd for have unix information

Hello, I'm running a Samba 4.3.3 install on FreeBSD 8.4 (ZFS) in domain mode with passdb tdb backend. The databases and config files are the current versions of an install that I think started in the 1.9.x version range back in the late 90s (I can't remember exactly--it's been a long time!) and smbpasswd days. I'm now trying to convert to an AD install using the classicupgrade

On 19/03/16 17:16, Sonic wrote: > On Fri, Mar 18, 2016 at 4:04 PM, Andrew Bartlett <abartlet at samba.org> wrote: >> The upgrade code assumes you run on the same host. I realise now that >> folks doing an upgrade use that an an opportunity to upgrade hardware, >> and keep old systems as fallbacks, so the assumptions cause trouble. >> >> Make the new host

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

Testing this "classic upgrade" scenario on a test server and have some issues. I'm using the Sernet 4.2.1 packages on Debian Wheezy. I copied the required tdb files and the smb.conf to the new test server (named WHEEZY). Edited the smb.conf to reflect the new host/netbios name of WHEEZY (remember that I want to keep the old PDC in service afterword for file and print sharing duties

On 07/03/16 19:04, Sonic wrote: > Sorry for the long post but attempted this several over the past year > with no success but staying on an NT4 domain is no longer viable. Need > to get this resolved so hopefully there will be a clue somewhere in > this montage. > > The current PDC is samba-3.6.25 running on Gentoo using tdbsam backend. > The new AD will be a Debian LXC

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

On Fri, Mar 18, 2016 at 2:39 PM, Andrew Bartlett <abartlet at samba.org> wrote: > Exactly. Think about it a little - how can it determine the group > membership, if the users/groups do not exist locally on the host doing > the migration? To clarify then: Do I need both the users and groups on the new host as they are on the old host, or just the groups? Is there any constraint

Hello, I'm testing samba4. I've setup a small samba3+ldap pdc, and then I tried a classicupgrade, but I can't pass step 4 of the howto. ubuntu at samba4:~/samba4$ /usr/local/samba/sbin/samba -V Version 4.1.0pre1-GIT-899cdc4 ubuntu at samba4:~/samba4$ sudo /usr/local/samba/bin/samba-tool domain classicupgrade --realm=example.com --dbdir=/root/samba /root/samba/smb.conf Reading

I am attempting to migrate a Slackware server with Samba 4.12.3 from an NT style domain to AD. I have done this about 7-8 times on other servers in the past following the instructions on Samba's wiki. This time however, the upgrade process is failing completely to import any users or groups from the NT domain. I have enclosed below the output of the classicupgrade command - I can't

Hi all, I have a question about memory usage and IPC$ share. I'am auditing the swap usage of my server because I already have a problem with a full swap. I see that the smbd process take < 200Mo on swap : Example : PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 24429 lge 15 0 197m 39m 14m S 0.3 1.0 0:15.17 smbd but some process use more than 200Mo