[Samba] Doman join issues
Praveen Ghimire
PGhimire at sundata.com.au
Tue May 7 06:25:03 UTC 2019
Hi Rowland/Louis,
Thank you for pointing out to the correct packages list. As it was a test box , I was able to run up a new one with the packages highlighted by Louis.
pt install samba winbind ntp bind9 binutils ldb-tools krb5-user libnss-winbind libpam-winbind
Following the github page, I configured the box and ran the upgrade but came with the same issue. There was an error in the actual migration which I hadn’t noticed before
PANIC (pid 512): Security context active token stack underflow!
It turns out the LXC container I was using needs to run in a priviledge mode. I ran up another container and was able to run the migration.
Regards,
Praveen Ghimire
-----Original Message-----
From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Rowland Penny via samba
Sent: Monday, 6 May 2019 10:42 PM
To: samba at lists.samba.org
Subject: Re: [Samba] Doman join issues
On Mon, 6 May 2019 11:12:17 +0000
Praveen Ghimire <PGhimire at sundata.com.au> wrote:
> Hi Rowland,
>
> Sorry about the confusion. It is Ubuntu 18.04 with Samba 4.7.6
>
> I have a script that installs the following
>
> apt-get install -y acl attr autoconf bind9utils bison build-essential
> \ debhelper dnsutils docbook-xml docbook-xsl flex gdb libjansson-dev \
> libacl1-dev libaio-dev libarchive-dev libattr1-dev libblkid-dev
> libbsd-dev \ libcap-dev libcups2-dev libgnutls28-dev libjson-perl \
> libldap2-dev libncurses5-dev libpam0g-dev libparse-yapp-perl \
> libpopt-dev libreadline-dev nettle-dev perl perl-modules pkg-config
> \ python-all-dev python-crypto python-dbg python-dev python-dnspython
> \ python3-dnspython python-markdown python3-markdown \
> python3-dev xsltproc zlib1g-dev liblmdb-dev lmdb-utils
> libnss-winbind apt-get install -y krb5-user apt-get install -y
> python-gpgme python3-gpgme
>
> I found that the python-gpgme and pythom3-gpgme gave error about
> dependencies. Apart from I am just installing samba, samba-common and
> bind9
Big problems there, you are installing the packages to build Samba and you have installed python3 packages, you do not need these for 4.7.6, you need python2
>
> The current production server (non-AD) is running Ubuntu 16.04 (Samba
> 4.3.11). Our plan is to run up a new Ubuntu 18.04 server ,transfer the
> config. Then let the server run for a few days to make sure
> everything works fine pre-migration. Then migrate to AD
>
> I have been testing the above in an Ubuntu 18.04 environment. It seems
> to work i.e. joining machines to domain, accessing shares etc.
> I then run the classicupgrade. The issues I've highlighted is post the
> classicupgrade.
I personally would have stuck with 16.04 to do the classicupgrade, then, after the upgrade, join a new 18.04 AD DC to that, transfer the FSMO roles and demote the 16.04 DC.
Rowland
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________
More information about the samba
mailing list