Description of problem: sealert fails to start with undefined symbol: fsetfilecon_raw error Version-Release number of selected component (if applicable): rpm -q setroubleshoot setroubleshoot-1.10.1-1.fc7 How reproducible: always Steps to Reproduce: 1.sealert -b 2. 3. Actual results: sealert -b Traceback (most recent call last): File "/usr/bin/sealert", line 104, in <module> from setroubleshoot.analyze import * File "/usr/lib/python2.5/site-packages/setroubleshoot/analyze.py", line 29, in <module> from setroubleshoot.avc_audit import * File "/usr/lib/python2.5/site-packages/setroubleshoot/avc_audit.py", line 28, in <module> import selinux File "/usr/lib/python2.5/site-packages/selinux.py", line 7, in <module> import _selinux ImportError: /usr/lib/python2.5/site-packages/_selinux.so: undefined symbol: fsetfilecon_raw Expected results: to see browser Additional info: I haven't run sealert in f7 due to this bug #237134 and as it was a duplicate of another bug which was recently closed, I gave it a go again this time it crashes out before starting. kde desktop
Things just changed due to koji :-) rpm -q rpm -q selinux-policy-targeted selinux-policy setroubleshoot setroubleshoot-server libselinux libselinux-devel libselinux-python selinux-policy-targeted-2.6.4-45.fc7 selinux-policy-2.6.4-45.fc7 setroubleshoot-1.10.6-1.fc7 setroubleshoot-server-1.10.6-1.fc7 libselinux-2.0.14-8.fc7 libselinux-devel-2.0.14-8.fc7 libselinux-python-2.0.14-8.fc7 [root@dexterFC ~]# sealert -b Traceback (most recent call last): File "/usr/bin/sealert", line 107, in <module> from setroubleshoot.analyze import * File "/usr/lib/python2.5/site-packages/setroubleshoot/analyze.py", line 28, in <module> from setroubleshoot.avc_audit import * File "/usr/lib/python2.5/site-packages/setroubleshoot/avc_audit.py", line 49, in <module> my_context = AvcContext(selinux.getcon()[1]) TypeError: getcon() takes exactly 1 argument (0 given)
Thank you for reporting this. The problem is in libselinux, there was a bad build and the swig bindings did not update properly. Many of the entry points in libselinux-python-2.0.14-8.fc7 have an extra parameter which should not be there. A new build is being prepared and should be available shortly in koji. Changing the component to libselinux and owner to dwalsh.
ok thanks for adjusting to right component and generally pointing me in the right direction :-) grabbed these from koji: libselinux-2.0.14-9.fc7 libselinux-devel-2.0.14-9.fc7 libselinux-python-2.0.14-9.fc7 the browser starts with sealert -S but cannot connect to /var/run/setroubleshoot/setroubleshoot_server trying to start and restart setroubleshoot from system-config-services brings up an error dialog with no info.
This is in logs after failure. Sep 27 19:47:41 dexterFC setroubleshoot: [rpc.ERROR] attempt to open server connection failed: No such file or directory
Are you seeing avc errors?
no avc's in audit.log
bugzilla is back! to be clear no avc denials in audit.log
I think you also need selinux-policy-2.6.4-45.fc7.src.rpm Which should be going in fedora-testing.
Yep got it see comment #1
see comment #12 in bug 289371, you may be hit by the same thing. From your description it sounds like the setroubleshootd daemon is not starting. If after the reboot that the above bugzilla suggests the problem persists then please check the contents of /var/log/setroubleshoot/setroubleshootd.log and see if there are tracebacks or error messages, if not we can try running the daemon in the foreground in verbose mode, but lets try the other options first.
ok sorry for the noise I forgot to turn selinux back on! a reboot and relabel later and everything is fine. closing this bug before any one notices :-)