Hide Forgot
Description of problem: Same as Fedora bug 679596 Cannot run system-config-selinux Version-Release number of selected component (if applicable): How reproducible: every time Steps to Reproduce: 1.sudo system-config-selinux 2. 3. Actual results: could not open interface info [/var/lib/sepolgen/interface_info] Expected results: open Selinux configuration gui Additional info: Indiana University server
I believe the bug report should belong to policycoreutils (not selinux-policy) component.
Harry were you running this on a disabled machine?
Selinux is NOT enabled. So are you saying to enable Selinux then try the system-config-selinux utility?
No just checking if something else was wrong. It should not blow up with this, but the reason the file does not exists is SELinux is disabled. We don't ususally test the selinux config tool on a disabled machine.
I see. I have just reinstalled all the Selinux packages and configured for permissive mode. I want tp build a module for Big Brother to run under Selinux. I have done this on our RHES 5.x servers without a problem. I cannot get any Selinux GUI utility to run nor does "setenforce Permissive" work.
I managed to get Selinux running in permissive mode, but still get same error trying to run system-config-selinux: [root@electron ~]# sestatus SELinux status: enabled SELinuxfs mount: /selinux Current mode: permissive Mode from config file: permissive Policy version: 24 Policy from config file: targeted [root@electron ~]# system-config-selinux could not open interface info [/var/lib/sepolgen/interface_info] [root@electron ~]#
does # sepolgen-ifgen return errors.
No it does not.
Does /var/lib/sepolgen/interface_info exist now?
It does exist.
Now system-config-selinux runs!
I just finished creating the policy module, so far it is working. I was able to enable Selinux via the GUI on RHES5. This time I had to edit the /etc/selinux/config then reboot twice. Shouldn't I be able to work with system-config-selinux without making the config file edit?
Thanks all. by the way Daniel, it is your article I used as the procedure to build the policy module. Harry
Yes this is a bug in policycoreutils. you should be able to at least run the app to turn SELinux on on a disabled system.
Fixed in policycoreutils-2.0.83-19.2.el6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1637.html