Created attachment 667938 [details] sealert -l running under strace, killed when stuck on poll() Description of problem: This probably belongs to setroubleshoot-server, but I couldn't find the component above. When troubleshooting an SElinux AVC denial, I ran sealert -l <guid>. The command took multiple minutes to return. I thought it had hung, so I ran it again under strace. I saw it stuck on a poll(), so I killed it. I ran it again, and it eventually completed in 3-4 minutes. strace log attached (stuck on poll unt il I killed it). Version-Release number of selected component (if applicable): 3.1.15-1.fc17 How reproducible: Repro'ed for me multiple times until I let it finish. It doesn't repro anymore (caching results?) Actual results: Hangs for a while Expected results: Completes soon Additional info: Attached strace.
Strange, I have no idea why this would take a long time, and I have never seen it before. If you kill setroubleshootd, do you see the same behaviour? killall -9 setroubleshootd sealert -l <guid>. I guess if you have a massive /var/lib/setroubleshoot/setroubleshoot_database.xml
Unfortunately, as I said above, once I let command run to completion, I couldn't get the issue to repro anymore. And my setroubleshoot_database.xml is only 158076 bytes; I'm not sure that's massive. Does my strace help in any way? Any reason to be stuck on the poll()? Could it somehow be a network timeout?
sealert is really not doing much network, or at least should not, It is possibly connecting to X. But it should connect to setroubleshootd and dump its output to the screen, or to an X Window Browser.