PDA

View Full Version : selinx, ypbind and Fedora 27 upgrade



hcaley
16th November 2017, 07:47 PM
I upgraded my stock Fedora 26 VM to Fedora 27 via DNF. This seems to break ypbind. It works fine with SELinux in "permissive mode". In "enforcing mode", I get the following error trying to start ypbind from systemctl. Not sure what to do about it.


● ypbind.service - NIS/YP (Network Information Service) Clients to NIS Domain Binder
Loaded: loaded (/usr/lib/systemd/system/ypbind.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2017-11-16 10:43:27 PST; 7s ago
Process: 2512 ExecStart=/usr/sbin/ypbind -n $OTHER_YPBIND_OPTS (code=exited, status=127)
Process: 2511 ExecStartPre=/usr/sbin/setsebool allow_ypbind=1 (code=exited, status=0/SUCCESS)
Process: 2508 ExecStartPre=/usr/libexec/ypbind-pre-setdomain (code=exited, status=0/SUCCESS)
Main PID: 2512 (code=exited, status=127)

Nov 16 10:43:27 localhost.localdomain systemd[1]: Starting NIS/YP (Network Information Service) Clients to NIS Domain B
Nov 16 10:43:27 localhost.localdomain setsebool[2511]: The allow_ypbind policy boolean was changed to 1 by root
Nov 16 10:43:27 localhost.localdomain ypbind[2512]: /usr/sbin/ypbind: error while loading shared libraries: libnsl.so.2
Nov 16 10:43:27 localhost.localdomain systemd[1]: ypbind.service: Main process exited, code=exited, status=127/n/a
Nov 16 10:43:27 localhost.localdomain systemd[1]: Failed to start NIS/YP (Network Information Service) Clients to NIS D
Nov 16 10:43:27 localhost.localdomain systemd[1]: ypbind.service: Unit entered failed state.
Nov 16 10:43:27 localhost.localdomain systemd[1]: ypbind.service: Failed with result 'exit-code'.