SAMBA_4.11.14... not found

The most recent openSUSE update that caused me to reboot also disabled my SAMBA share. YaST believes everything is working fine, but OS/X is no longer able to see the share. So, something changed and what that was is not obvious. I’ve been unable to use Photoshop for a full day. (My openSUSE box manages a RAID array.)

** #** systemctl  status nmb.service|cat
● nmb.service - Samba NMB Daemon
   Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2021-05-03 08:42:26 PDT; 2h 28min ago
  Process: 14372 ExecStart=/usr/sbin/nmbd --foreground --no-process-group $NMBDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 14372 (code=exited, status=1/FAILURE)

May 03 08:42:26 bach systemd[1]: Starting Samba NMB Daemon...
May 03 08:42:26 bach nmbd[14372]: /usr/sbin/nmbd: /usr/lib64/samba/libreplace-samba4.so: version `SAMBA_4.11.14_GIT.247.8C858F7EE14LP152.3.19.1_SUSE_OS15.0_X86_64' not found (required by /usr/lib64/libwbclient.so.0)
May 03 08:42:26 bach nmbd[14372]: /usr/sbin/nmbd: /usr/lib64/samba/libwinbind-client-samba4.so: version `SAMBA_4.11.14_GIT.247.8C858F7EE14LP152.3.19.1_SUSE_OS15.0_X86_64' not found (required by /usr/lib64/libwbclient.so.0)
May 03 08:42:26 bach systemd[1]: nmb.service: Main process exited, code=exited, status=1/FAILURE
May 03 08:42:26 bach systemd[1]: Failed to start Samba NMB Daemon.
May 03 08:42:26 bach systemd[1]: nmb.service: Unit entered failed state.
May 03 08:42:26 bach systemd[1]: nmb.service: Failed with result 'exit-code'.

Since zypper should be keeping all this stuff in sync, I really don’t know how to deal with the required version not being found.

What I would do first is

systemctl restart smb nmb
systemctl status smb nmb
systemctl enable smb
systemctl enable nmb

If that fixed it - then done

If not I would remove and reinstall samba

zypper rm samba
zypper in samba
systemctl restart smb nmb
systemctl status smb nmb
systemctl enable smb
systemctl enable nmb

My 2 cents

Nope. I went through all that with the output from

systemctl status nmb.service

above, but:

I would remove and reinstall samba

zypper rm samba ; zypper in samba...

Yep. That did the trick. Looks like SuSE screwed up the update and I didn’t consider a remove/reinstall.

THANK YOU, THANK YOU, THANK YOU!!!