[SOLVED] Samba broke after upgrading from Fedora 33 to Fedora 34

Hi,

After upgrading from Fedora 33 to Fedora 34, samba broke, and the smb and nmb services are not working. Any suggestions on how to fix this issue. Below are the errors that I am getting.

Thanks in advance,

Bellsal

-----------------------------------------

[root@LinuxSrv lib]# systemctl status smb

x smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2021-10-09 18:09:11 MST; 1h 38min ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 32914 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=127)
Main PID: 32914 (code=exited, status=127)
CPU: 3ms

Oct 09 18:09:11 LinuxSrv.bellsaluna systemd[1]: Starting Samba SMB Daemon...
Oct 09 18:09:11 LinuxSrv.bellsaluna smbd[32914]: /usr/sbin/smbd: error while loading shared libraries: libldap-2.4.so.2: cannot open shared object file: No such file or directory
Oct 09 18:09:11 LinuxSrv.bellsaluna systemd[1]: smb.service: Main process exited, code=exited, status=127/n/a
Oct 09 18:09:11 LinuxSrv.bellsaluna systemd[1]: smb.service: Failed with result 'exit-code'.
Oct 09 18:09:11 LinuxSrv.bellsaluna systemd[1]: Failed to start Samba SMB Daemon.

----------------------------------------------------------

[root@LinuxSrv lib]# journalctl -xeu smb.service
-- An ExecStart= process belonging to unit smb.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 127.
Oct 09 15:32:17 LinuxSrv.bellsaluna systemd[1]: smb.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailma.../systemd-devel
--
-- The unit smb.service has entered the 'failed' state with result 'exit-code'.
Oct 09 15:32:17 LinuxSrv.bellsaluna systemd[1]: Failed to start Samba SMB Daemon.
-- Subject: A start job for unit smb.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailma.../systemd-devel
--
-- A start job for unit smb.service has finished with a failure.
--
-- The job identifier is 6741 and the job result is failed.
Oct 09 18:09:11 LinuxSrv.bellsaluna systemd[1]: Starting Samba SMB Daemon...
-- Subject: A start job for unit smb.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailma.../systemd-devel
--
-- A start job for unit smb.service has begun execution.
--
-- The job identifier is 22752.
Oct 09 18:09:11 LinuxSrv.bellsaluna smbd[32914]: /usr/sbin/smbd: error while loading shared libraries: libldap-2.4.so.2: cannot open shared object file: No such file or directory
Oct 09 18:09:11 LinuxSrv.bellsaluna systemd[1]: smb.service: Main process exited, code=exited, status=127/n/a
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailma.../systemd-devel
--
-- An ExecStart= process belonging to unit smb.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 127.
Oct 09 18:09:11 LinuxSrv.bellsaluna systemd[1]: smb.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailma.../systemd-devel
--
-- The unit smb.service has entered the 'failed' state with result 'exit-code'.
Oct 09 18:09:11 LinuxSrv.bellsaluna systemd[1]: Failed to start Samba SMB Daemon.
-- Subject: A start job for unit smb.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailma.../systemd-devel
--
-- A start job for unit smb.service has finished with a failure.
--
-- The job identifier is 22752 and the job result is failed.

------------------

In Fedora 33, it was:
lrwxrwxrwx 1 root root 22 Sep 15 2020 /usr/lib64/libldap-2.4.so.2 -> libldap-2.4.so.2.10.13

In Fedora 34, it is:
lrwxrwxrwx 1 root root 23 Jun 10 09:03 libldap_r-2.4.so.2 -> libldap_r-2.4.so.2.11.5