From: Matthew Booth <mbooth@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Auditd hangs hard
Date: Tue, 12 Jun 2007 09:50:27 +0100 [thread overview]
Message-ID: <1181638227.26075.5.camel@localhost.localdomain> (raw)
In-Reply-To: <200706090759.06963.sgrubb@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1099 bytes --]
On Sat, 2007-06-09 at 07:59 -0400, Steve Grubb wrote:
> On Friday 08 June 2007 10:32:54 Matthew Booth wrote:
> > I have a test server on which, if left to its own devices, the audit
> > daemon will lock up hard.
>
> Does boosting the priority so auditd runs more often help? I think it defalts
> to 3, you can make it 10 for an experiment.
Thanks, Steve. This put me on the right track. It turns out that not
only is LSF very noisy, but it also runs itself with niceness -20.
Renicing it to -5 and running auditd at -10 fixes the problem. I've
asked the customer to raise an issue against LSF as this strikes me as a
bug.
It does strike me that audit could cope with overload much better,
though. If it's configured to drop messages rather than kill the system,
it could probably disable auditing entirely when the kernel buffer is
full, and only re-enable it when there's enough space.
Matt
--
Matthew Booth, RHCA, RHCSS
Red Hat, Global Professional Services
M: +44 (0)7977 267231
GPG ID: D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2007-06-12 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 14:32 Auditd hangs hard Matthew Booth
2007-06-09 11:59 ` Steve Grubb
2007-06-12 8:50 ` Matthew Booth [this message]
2007-06-12 16:45 ` Steve Grubb
2007-06-12 16:54 ` Matthew Booth
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=1181638227.26075.5.camel@localhost.localdomain \
--to=mbooth@redhat.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@redhat.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