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

[Rowland Penny]

On Tue, 5 Dec 2023 15:21:50 +0100
Joachim Lindenberg via samba <samba at lists.samba.org> wrote:

> I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 ->
> 4.19, but the Dc is not yet working again.

How did you upgrade ?
If I remember correctly, both 20.04 and 22.04 come with 4.15.13 (latest
Samba version available), so could it be that the upgrade from 20.04 to
22.04 managed to install unrequired packages ?
 
> 
> systemctl status samba-ad-dc shows:
> 
>  
> 
> 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)
> 
> Dec 05 12:48:39 cobra samba[749]:   task_server_terminate:
> task_server_terminate: [winbindd child process exited]
> 
> Dec 05 12:48:39 cobra systemd[1]: Started Samba AD Daemon.
> 
> Dec 05 12:48:39 cobra samba[694]: [2023/12/05 12:48:39.615787,  0]
> ../../source4/samba/process_prefork.c:630(prefork_child_pipe_handler)
> 
> Dec 05 12:48:39 cobra samba[694]:   prefork_child_pipe_handler:
> Parent 694, Child 719 exited with status 0
> 
> Dec 05 12:48:39 cobra samba[694]: [2023/12/05 12:48:39.622956,  0]
> ../../source4/samba/server.c:403(samba_terminate)
> 
> Dec 05 12:48:39 cobra samba[694]:   samba_terminate: samba_terminate
> of samba 694: winbindd child process exited
> 
> Dec 05 12:48:39 cobra systemd[1]: samba-ad-dc.service: Main process
> exited, code=exited, status=1/FAILURE
> 
> Dec 05 12:48:40 cobra systemd[1]: samba-ad-dc.service: Failed with
> result 'exit-code'.
> 
> Dec 05 12:48:40 cobra systemd[1]: samba-ad-dc.service: Consumed
> 1.340s CPU time.
> 
>  
> 
> I never compiled from sources as the path in the error messages
> suggest.

No, whilst you are correct that the paths refer to the source code,
they are like that with every Samba install, whether it is from a self
compiled Samba or from distro packages.
> Forcing reinstallation of all packages originating
> http://www.corpit.ru/mjt/packages/samba did not solve the issue.
> Where to I have to fix the erroneous paths?

Well, that is never going to work, forcing the reinstall of packages
that are already giving problems isn't likely to fix anything.

You have two options, if you can find and fix your problem, that would
be the preferred option, you would learn something and would know what
not to do in future.
Your second option, if you must get this fixed quickly (if someone is
shouting at you), demote the DC, wipe it and re-install the OS and then
join it as a new DC.

Rowland

> 
>  
> 
> Thanks, Joachim
> 
>  
> 
>  
>