All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Joe Zeff <joe@zeff.us>
Cc: selinux@tycho.nsa.gov
Subject: Re: Puzzling SELinux problem
Date: Thu, 06 Oct 2011 09:25:21 -0400	[thread overview]
Message-ID: <4E8DAC41.7060108@redhat.com> (raw)
In-Reply-To: <4E8CF584.2080708@zeff.us>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/05/2011 08:25 PM, Joe Zeff wrote:
> I'm running Fedora 14, fully updated, with SELinux.  Off and on
> I've had SELinux alerts from various WCG projects, but nothing
> major.  Recently, however, a badly written project started walking
> parts of /proc that it had no business in, causing large spews of
> alerts.  (BOINC runs in permissive mode, so nothing got blocked.)
> I've dealt with that by unselecting the project.  However, at one
> point I accidentally clicked on the alert icon twice.  It came up,
> showing details of the alert then vanished, as a second sealert
> window came up, blank.  That is, no alerts to show.  Since then,
> I'm still getting alerts, but none of them show up in the
> troubleshooter window.  I've tried restarting auditd without effect
> and deleting the database.  Nothing works.  If anybody on this list
> knows what I can do to correct this, please let me know.  You can 
> see what I'm describing at http://www.zeff.us/sealert.png
> 
> If this isn't the right list to put this on, please direct me to
> the right place.
> 
> -- This message was distributed to subscribers of the selinux
> mailing list. If you no longer wish to subscribe, send mail to
> majordomo@tycho.nsa.gov with the words "unsubscribe selinux"
> without quotes as the message.
> 
> 
Are you seeing a python crash in /var/log/messages or
/var/log/setroubleshoot

?

Can you email me your

/var/lib/setroubleshoot/setroubleshoot_database.xml

Then make sure setroubleshootd is not running.

# killall -9 -Z setroubleshootd_t
# > /var/lib/setroubleshoot/setroubleshoot_database.xml

SEtroubleshoot should start working again.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6NrEAACgkQrlYvE4MpobNngwCgvWqA8rzLWj+xKD9cwzajkeZI
LNQAoI5DJvQBUsFt9sYNvJKEPBIOSAY1
=e+zl
-----END PGP SIGNATURE-----

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2011-10-06 13:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06  0:25 Puzzling SELinux problem Joe Zeff
2011-10-06 13:25 ` Daniel J Walsh [this message]
2011-10-06 18:05   ` Joe Zeff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E8DAC41.7060108@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=joe@zeff.us \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.