Hide Forgot
Version-Release number of selected component: setroubleshoot-server-3.2.14-2.fc20 Additional info: reporter: libreport-2.1.9 cmdline: /usr/bin/python -Es /usr/sbin/setroubleshootd -f '' dso_list: python-libs-2.7.5-9.fc20.x86_64 executable: /usr/sbin/setroubleshootd kernel: 3.11.9-300.fc20.x86_64 runlevel: N 5 type: Python uid: 0 Truncated backtrace: analyze.py:388:lookup_signature:ProgramError: [Errno 1001] signature not found Traceback (most recent call last): File "/usr/lib64/python2.7/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) File "/usr/lib64/python2.7/site-packages/setroubleshoot/server.py", line 521, in goodbye database.save() File "/usr/lib64/python2.7/site-packages/setroubleshoot/analyze.py", line 344, in save self.prune() File "/usr/lib64/python2.7/site-packages/setroubleshoot/analyze.py", line 309, in prune self.delete_signature(sig, prune=True) File "/usr/lib64/python2.7/site-packages/setroubleshoot/analyze.py", line 426, in delete_signature siginfo = self.lookup_signature(sig) File "/usr/lib64/python2.7/site-packages/setroubleshoot/analyze.py", line 388, in lookup_signature raise ProgramError(ERR_NO_SIGNATURE_MATCH) ProgramError: [Errno 1001] signature not found Local variables in innermost frame: matches: [] siginfo: None self: <setroubleshoot.analyze.SETroubleshootDatabase object at 0x7f86f295ad10> sig: <setroubleshoot.signature.SEFaultSignature object at 0x4c09d90> Potential duplicate: bug 972510
Created attachment 834220 [details] File: backtrace
Created attachment 834221 [details] File: environ
Could you try to execute # killall -9 setroubleshootd # > /var/lib/setroubleshoot/setroubleshoot_database.xml and see if this happens again. If yes, please reopen the bug. Thank you.
(In reply to comment 3) Miroslav: I did that a while ago and I don't plan to do this every week, so I decided to consider this a bug, indeed. Please reopen.
(In reply to Andre Klapper from comment #4) > (In reply to comment 3) > Miroslav: I did that a while ago and I don't plan to do this every week, so > I decided to consider this a bug, indeed. Please reopen. Switching back to Assigned.
*** Bug 1057980 has been marked as a duplicate of this bug. ***
Did it happen when you were using sealert?
How would I find out if I "use sealert"? This is a Fedora 20 system (sometimes running GNOME, sometimes XFCE) and likely any SELinux settings are default settings.
Could you send the AVC you get when this happens. We do not see this happening else where.
Folks, either use clear steps, or link to a wikipage explaining how to do X. I have no idea how to "send the AVC" or what AVC even stands for. Seriously.
Sorry. ausearch -m avc,user_avc Will gather the AVC messages on your system. This could be large.
Haven't seen this problem for a while now. Might be closed.