Michael Tokarev
2023-Dec-05 16:55 UTC
[Samba] upgrade ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19
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
Michael Tokarev
2023-Dec-05 17:00 UTC
[Samba] upgrade ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19
05.12.2023 19:55, Michael Tokarev via samba: ..> 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 installedJust to clarify: samba-ad-dc is a dummy package for now, it does not have any files, just dependencies to collect all necessary parts of samba ad-dc, namely: samba itself, samba-vfs-modules, samba-dsdb-modules, and also samba-ad-provision packages (the latter is necessary if you want to create new domain). So you can install the same set of packages by your own and the result will be the same, - samba-ad-dc is just a convenient way to do that. And it is a new package too, that's why the prob went unnoticed so far. I'm waiting for the list of samba-related packages from your system. /mjt
Joachim Lindenberg
2023-Dec-05 17:04 UTC
[Samba] upgrade ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19
Hi Michael, I figured out myself that samba-ad-dc or samba does not upgrade everything and explicitly asked for reinstall of all packages originating from your repo. The output ii ldb-tools 2:2.8.0+samba4.19.3+dfsg-1~jammy amd64 LDAP-like embedded database - tools ii libldb2:amd64 2:2.8.0+samba4.19.3+dfsg-1~jammy amd64 LDAP-like embedded database - shared library ii python3-ldb 2:2.8.0+samba4.19.3+dfsg-1~jammy amd64 Python 3 bindings for LDB ii python3-samba 2:4.19.3+dfsg-1~jammy amd64 Python 3 bindings for Samba ii samba 2:4.19.3+dfsg-1~jammy amd64 SMB/CIFS file, print, and login server for Unix ii samba-ad-provision 2:4.19.3+dfsg-1 all Samba files needed for AD domain provision ii samba-common 2:4.19.3+dfsg-1 all common files used by both the Samba server and client ii samba-common-bin 2:4.19.3+dfsg-1~jammy amd64 Samba common files used by both the server and the client ii samba-dsdb-modules:amd64 2:4.19.3+dfsg-1~jammy amd64 Samba Directory Services Database ii samba-libs:amd64 2:4.19.3+dfsg-1~jammy amd64 Samba core libraries ii samba-vfs-modules:amd64 2:4.19.3+dfsg-1~jammy amd64 Samba Virtual FileSystem plugins confirms that (or am I misinterpreting anything?) Thanks, Joachim
Michael Tokarev
2023-Dec-05 19:22 UTC
[Samba] upgrade ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19
05.12.2023 19:55, Michael Tokarev via samba:> 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.... We exchanged some emails off-list. The problem was that during upgrade, winbind package has been *uninstalled* from the system. And sure thing, while samba ad-dc tried to execute winbind, it failed, with the messages above. After installing winbind (and libnss-winbind which has also been uninstalled), the DC instantly started working. I'm not yet sure why winbind has been uninstalled during this whole upgrade process. Maybe Joachim can find some info in the logs, - grepping /var/log/dpkg.log* for winbind might give some clues. It will be interesting to find out what happened. With fixed samba-ad-dc versioned depends: things should work again. I'll upload fixed packages in a few days. Once again, this brokeness of samba-ad-dc deps is just inconvenience, nothing more, since the package itself is empty and only used to collect all deps of AD-DC functionality in one package. /mjt