Hi guys,

One of my EC2 instances running SLES12.4 is unable to start samba service .

sclosdm:~ # service smb start
Job for smb.service failed because the control process exited with error code. See "systemctl status smb.service" and "journalctl -xe" for details.
sclosdm:~ # service smb status
* smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2019-11-07 04:15:46 UTC; 8s ago
Process: 19347 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=127)
Process: 19343 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS)
Main PID: 19347 (code=exited, status=127)

Nov 07 04:15:46 sclosdm systemd[1]: Starting Samba SMB Daemon...
Nov 07 04:15:46 sclosdm smbd[19347]: /usr/sbin/smbd: symbol lookup error: /usr/lib64/samba/libsmbd-base-samba4.so: undefined symbol: ippGetValueTag
Nov 07 04:15:46 sclosdm systemd[1]: smb.service: Main process exited, code=exited, status=127/n/a
Nov 07 04:15:46 sclosdm systemd[1]: Failed to start Samba SMB Daemon.
Nov 07 04:15:46 sclosdm systemd[1]: smb.service: Unit entered failed state.
Nov 07 04:15:46 sclosdm systemd[1]: smb.service: Failed with result 'exit-code'.
sclosdm:~ # nm -D /usr/lib64/samba/libsmbd-base-samba4.so | grep ippGetValueTag
U ippGetValueTag

Regards,
Abhinav