linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Matthew Chao <mathewchao@gmail.com>
Cc: linux-audit@redhat.com
Subject: Re: How to monitor audit/audispd killed
Date: Mon, 04 Jan 2016 14:43:44 -0500	[thread overview]
Message-ID: <2955652.6SqtRXJnWL@x2> (raw)
In-Reply-To: <CAH8ERfawFuZQiiy7hSfjoBd97VOSsmnLDpCgcHw=k3JmX9Mf8g@mail.gmail.com>

On Tuesday, January 05, 2016 03:29:31 AM Matthew Chao wrote:
> >You have a race condition where auditd gets a signal to shutdown and an
> event indicating that shutdown is occurring. On shutdown, the audit daemon
> does not alter the rules or whether auditing is enabled. (This was to get
> shutdown AVCs for selinux.) There is a chance that your event is in syslog's
> files.
> 
> For clarity, I am still not sure whether audit rules can be written to
> monitor auditd/auispd killed or not (syslog was disabled under my
> circumstances ).

You cannot audit the audit daemon's pid. Otherwise servicing an event could 
create several more events which cause even more and you get an exponential 
increase in logging until it dies.

You can watch audispd, but I don't think that will help anything.


> If yes, could you give me some tips? Thanks.

The audit daemon is required to log some information about why it shutdown. If 
you have a daemon_end event, this is the required information. Is there 
something not in the event that you need?

-Steve

  reply	other threads:[~2016-01-04 19:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 12:10 How to monitor audit/audispd killed Matthew Chao
2016-01-04 14:12 ` Richard Guy Briggs
2016-01-04 19:49   ` Matthew Chao
2016-01-04 14:32 ` Steve Grubb
2016-01-04 19:29   ` Matthew Chao
2016-01-04 19:43     ` Steve Grubb [this message]
2016-01-04 19:51       ` Matthew Chao
2016-01-05 10:08       ` Matthew Chao
2016-01-05 14:10         ` Steve Grubb
2016-01-05 16:12           ` Matthew Chao
2016-01-05 17:48             ` Steve Grubb

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=2955652.6SqtRXJnWL@x2 \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=mathewchao@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).