samba - Jul 2024 - new DC via clone..

in an attempt to analyze the misbehaviour of my clone I compiled samba (version
4.19.7) from sources, following
https://wiki.samba.org/index.php/Build_Samba_from_Source#make.
When I entered "make install" however, it started a new compile/link
with even more sources [yy/5891] after compilation of preceeding make succeeded
[xx/4536]. This is not what I expected to happen - imho install just copies
files. Any ideas?
Then I also tried ./configure to change the pathes and figured out, the
"..." is probably not required and one could supply multiple options
in a single call, correct?
After changing the paths, make, make install, and systemctl start samba-ad-dc I
get
"exit_daemon: daemon failed to start: Samba failed to prime database, error
code 22"
As I replaced version 4.19.7-Ubuntu: why can the database formats differ? Or
what else could have gone wrong?
Thanks,
Joachim
> -----Urspr?ngliche Nachricht-----
> Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Rowland
> Penny via samba
> Gesendet: Montag, 22. Juli 2024 17:49
> An: samba at lists.samba.org
> Cc: Rowland Penny <rpenny at samba.org>
> Betreff: Re: [Samba] new DC via clone..
> 
> On Mon, 22 Jul 2024 16:48:59 +0200
> Joachim Lindenberg via samba <samba at lists.samba.org> wrote:
> 
> > Hello Rowland,
> > there can be a lot more services than just the OS and Samba-AD-DC.
> 
> Just like Microsoft, Samba doesn't recommend using a DC for other
services
> and running it in some form of VM doesn't make it different.
> 
> > As
> > a must have you have to configure bind, and in my specific case I have
> > also a pi-hole and stubby running with docker in order to provide
> > complete DNS services on the DCs. Cloning is definitely a huge saving
> > of time than starting from scratch. Everybody except probably Samba
> > today uses clones where possible.
> 
> As I said, I wouldn't clone a DC, but a quick internet search turns up
that you
> can clone a Microsoft AD DC, provided a few criteria are met:
> 
> It is only running software essential for the DC.
> It holds most, if not all, the FSMO roles.
> Can be powered down for a short while.
> It is best to be already virtualised.
> 
> Your clone does not seem to match the above.
> 
> You are having problems, which may be just down to Samba, or they could be
> due to an interaction between Samba and some other piece of software.
> 
> I suggest you start with a fresh VM, install Samba in that and join it as a
DC
> (using the internal dns server), if that works okay, then add Bind and keep
> adding things until it stops working, at which point you may be able to
work
> out what the problem is. If the new Samba gives you the same problem that
> you are having now, then it will be less software in the way when trying to
> sort out the problem.
> 
> Rowland
> 
> 
> 
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

On Tue, 23 Jul 2024 15:45:21 +0200
Joachim Lindenberg via samba <samba at lists.samba.org> wrote:
> in an attempt to analyze the misbehaviour of my clone I compiled
> samba (version 4.19.7) from sources, following
> https://wiki.samba.org/index.php/Build_Samba_from_Source#make. When I
> entered "make install" however, it started a new compile/link
with
> even more sources [yy/5891] after compilation of preceeding make
> succeeded [xx/4536]. This is not what I expected to happen - imho
> install just copies files. Any ideas? 
Yes, it does that, not really compiling much, more creating man pages
etc, if I remember correctly.
> Then I also tried ./configure
> to change the pathes and figured out, the "..." is probably not
> required and one could supply multiple options in a single call,
> correct?
If you run './configure --help' it will give you a full list of its
options. However, it is a bit more complicated than just setting paths,
there made old bits of your original Samba left behind if you just
install a self compiled Samba over a distro package Samba.
If you are going down this path, then I would suggest either building
Samba as distro packages or into the default /usr/local/samba .
 
> After changing the paths, make, make install, and systemctl
> start samba-ad-dc I get "exit_daemon: daemon failed to start: Samba
> failed to prime database, error code 22" As I replaced version
> 4.19.7-Ubuntu: why can the database formats differ? Or what else
> could have gone wrong? Thanks, Joachim
If I understand that correctly, you built Samba on an existing DC and
installed your Samba over the existing distro Samba. If that is the
case, then I don't think that was a good idea.

Rowland
> 
>