samba - Dec 2023 - upgrade ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19

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.

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. 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?

 

Thanks, Joachim

It?s always recommend to demote the DC, upgrade samba, and join the DC again.
Did you do it this way ?

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

Instead of troubleshooting, which you can of course do, I?d demote (or
force-demote), reinstall and re join.

http://samba.bigbird.es/doku.php?id=samba:upgrade-sama

LP
On 5 Dec 2023 at 15:45 +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.
>
> 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.
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?
>
>
>
> Thanks, Joachim
>
>
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba

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

05.12.2023 17:21, Joachim Lindenberg via samba:
> 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.
> 
> 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.
Please show versions of all samba-related packages you've installed.

  dpkg -l | grep samba

It looks like there's a bug in my packaging (in rebuild of samba for
different distributions).  And the bug is with samba-ad-dc package
only.  I just tried installing samba-ad-dc from my repository on a
ubuntu jammy system, and it doesn't work - it doesn't install:

  The following packages have unmet dependencies:
   samba-ad-dc : Depends: samba (>= 2:4.19.3+dfsg-1) but
2:4.19.3+dfsg-1~jammy is to be installed

That's a problem in versioned depends of samba-ad-dc, the forgotten
tilde (~) after the version number.

/mjt