[Samba] upgrade ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19

Michael Tokarev mjt at tls.msk.ru
Tue Dec 5 15:12:31 UTC 2023


05.12.2023 17:51, Luis Peromarta via samba :
> It’s always recommend to demote the DC, upgrade samba, and join the DC again. Did you do it this way ?

This is rarely needed and in almost all cases is unnecessary and just an extra work.
The only good reason to do that is when you upgrade a very old version of samba,
skipping 5..10 or more releases in between, and even there it almost always work.

> You may have a broken DC, or a broken installation.

If there's a broken DC or a broken installation, there are 2 questions:
1) how to fix it, and 2) how it broke.  By reinstalling from scratch,
we'll never know what's going on.  It might be an easiest way to solve
immediate problem though.

Also, I don't quite understand what a "broken installation" is.  Any decent
package manager (and dpkg is definitely one of these) ensures the installation
is the same no matter how you install or upgrade the system, - unless you
mess with files behind package manager's back. So the only way an installation
might become "broken" is when the packages one install are broken, - and it
wont help to reinstall these broken packages for sure, it's just a total
waste of time.

Samba should not crash like this in any case, and it's our job to find out
what's going on and to fix it.  It is supposed to work.

I'll try to run ubuntu in a chroot and at least start an ad-dc in there, -
I don't do that myself.  Maybe today.

>> Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] ../../source4/samba/service_task.c:36(task_server_terminate)

Hm. It needs -ffile-prefix-map=../../= to the compiler. Ok.

..
>> I never compiled from sources as the path in the error messages suggest.

How a path in the error messages suggest that?

/mjt



More information about the samba mailing list