Description of problem:
Startup error message occurs after update to v 4.7.3
Version-Release number of selected component (if applicable):
V 4.7.3
How reproducible:
Error presents itself after reboot or manual startup using systemctl
Steps to Reproduce:
1. systemctl start nmb smb
2.
3.
Actual results:
journalctl -u nmb -b:
Dec 03 11:08:35 roxie.blkdiamonds.lan systemd[1]: Starting Samba NMB Daemon...
Dec 03 11:08:40 roxie.blkdiamonds.lan nmbd[1591]: /usr/sbin/nmbd: error while loading shared libraries: libaesni-intel-samba4.so: cannot enable executab
Dec 03 11:08:46 roxie.blkdiamonds.lan systemd[1]: nmb.service: Main process exited, code=exited, status=127/n/a
Dec 03 11:08:46 roxie.blkdiamonds.lan systemd[1]: Failed to start Samba NMB Daemon.
Dec 03 11:08:46 roxie.blkdiamonds.lan systemd[1]: nmb.service: Unit entered failed state.
Dec 03 11:08:46 roxie.blkdiamonds.lan systemd[1]: nmb.service: Failed with result 'exit-code'.
Expected results:
Normal clean startup for Samba services
Additional info:
Read Samba execstack discussion here: http://samba.2283325.n4.nabble.com/libaesni-intel-samba4-so-and-execstack-flag-td4725770.html
Installing execstack 0.5.0-13.fc27 and rebooting did not resolve complaint. Selinux is not complaining. Other than an attempt to downgrade have no idea how to troubleshoot.
Comment 1Alexander Bokovoy
2017-12-04 08:20:51 UTC
Wrong component.
Comment 2Alexander Bokovoy
2017-12-04 08:22:07 UTC
*** Bug 1520252 has been marked as a duplicate of this bug. ***
Comment 3Fabiano FidĂȘncio
2017-12-04 10:57:39 UTC
*** Bug 1520332 has been marked as a duplicate of this bug. ***
Comment 4Fedora Update System
2017-12-04 13:34:41 UTC