[RESOLVED] SAMBA Upgrade

[vig]

Good morning,

currently using samba Version 4.10.17-Debian Stretch, I wish to switch to the latest Release (4.14.4).

I am encountering this problem:

#cat /etc/apt/sources.list.d/tissamba.list

Code: Select all

deb https://samba.tranquil.it/debian/samba-4.14.4/ stretch main

#apt update

Code: Select all

Err:10 https://samba.tranquil.it/debian/samba-4.14.4 stretch/main amd64 Packages
  404  Not Found
...
Reading package lists... Done
W: The repository 'https://samba.tranquil.it/debian/samba-4.14.4 stretch Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://samba.tranquil.it/debian/samba-4.14.4/dists/stretch/main/binary-amd64/Packages  404  Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.

Is there a problem with your deposits?
I've tested all the versions, it's the same.

THANKS

[dcardon]

Perhaps because the distribution is a stretch?

[vig]

Hello,

even leaving the repository on my current version, I get the same error message.

[wapt42]

Good morning

I personally encounter an error during the updates of the tranquil.it samba repositories

Code: Select all

Distributor ID: Debian
Description:    Debian GNU/Linux 9.13 (stretch)
Release:        9.13
Codename:       stretch

Code: Select all

deb https://samba.tranquil.it/debian/samba-4.10/ stretch main

Code: Select all

Err:7 https://samba.tranquil.it/debian/samba-4.10 stretch Release
  404  Not Found
E: The repository 'https://samba.tranquil.it/debian/samba-4.10 stretch Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

[dcardon]

I have updated the doc https://dev.tranquil.it/samba/en/samba_ ... ebian.html to properly mention Buster and a more recent version of Samba.

[wapt42]

Cool, thanks, I'll test it and give feedback.

[wapt42]

After the upgrade from Stretch to Buster and the switch from Samba AD 4.10 to 4.13, Bind9 breaks:

Code: Select all

● bind9.service - BIND Domain Name Server
   Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2021-06-03 12:40:04 CEST; 6ms ago
     Docs: man:named(8)
  Process: 2872 ExecStart=/usr/sbin/named $OPTIONS (code=exited, status=1/FAILURE)

juin 03 12:40:04 srvads2.ad.atdqm.tech named[2873]: Loading 'ad.atdqm.tech' using driver dlopen
juin 03 12:40:04 srvads2.ad.atdqm.tech named[2873]: dlz_dlopen failed to open library '/usr/lib/x86_64-linux-gnu/samba/bind9/dlz_bind9_10.so' - /usr/lib/x86_64-linux-gnu/samba/bind9/dlz_bind9_10.so: cannot open shared object file: No such file or directory
juin 03 12:40:04 srvads2.ad.atdqm.tech named[2873]: dlz_dlopen of 'ad.atdqm.tech' failed
juin 03 12:40:04 srvads2.ad.atdqm.tech named[2873]: SDLZ driver failed to load.
juin 03 12:40:04 srvads2.ad.atdqm.tech named[2873]: DLZ driver failed to load.
juin 03 12:40:04 srvads2.ad.atdqm.tech named[2873]: loading configuration: failure
juin 03 12:40:04 srvads2.ad.atdqm.tech named[2873]: exiting (due to fatal error)
juin 03 12:40:04 srvads2.ad.atdqm.tech systemd[1]: bind9.service: Control process exited, code=exited, status=1/FAILURE
juin 03 12:40:04 srvads2.ad.atdqm.tech systemd[1]: bind9.service: Failed with result 'exit-code'.
juin 03 12:40:04 srvads2.ad.atdqm.tech systemd[1]: Failed to start BIND Domain Name Server.
dpkg: erreur de traitement du paquet bind9 (--configure) :
 installed bind9 package post-installation script subprocess returned error exit status 1
Traitement des actions différées (« triggers ») pour man-db (2.8.5-2) ...
Traitement des actions différées (« triggers ») pour systemd (241-7~deb10u7) ...
Des erreurs ont été rencontrées pendant l'exécution :
 bind9

Do you have any ideas for a possible solution or another upgrade method?

[wapt42]

Okay, after having:

Removed bind9

Code: Select all

apt remove bind9

Perform an autoremoval

Installed the correct packages:

Code: Select all

apt install samba winbind libnss-winbind krb5-user smbclient ldb-tools python3-crypto

Code: Select all

apt install bind9

Rebooted the machine

It's in.

[dcardon]

Hello wapt42,

Samba comes with a BIND-DLZ module to allow Bind to query Samba's LDB databases directly (not elegant, but it currently works). The ABI (the communication API between Bind and the DLZ module) is dependent on the Bind 9 version and changes very frequently. Therefore, this can create a chicken-and-egg problem between Bind and DLZ module updates in some cases, as they will eventually become incompatible.

The best way to resolve this would be to make the queries using the LDAPI protocol, but there is currently no funding to fix this.

Now that you are on Debian 10 with a recent version, this shouldn't be a problem for future updates.

I'm marking the topic as [RESOLVED].

Best regards,

Denis