All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Tangren <bjt@usno.navy.mil>
Cc: linux-audit@redhat.com
Subject: Re: wierd audit problems on one RHEL ES4 box
Date: Fri, 13 Apr 2007 10:27:01 -0400	[thread overview]
Message-ID: <461F9335.9040205@usno.navy.mil> (raw)
In-Reply-To: <200704121014.18163.sgrubb@redhat.com>

Steve Grubb wrote:
> On Thursday 12 April 2007 10:08, Bill Tangren wrote:
>> Any ideas what is wrong?
> 
> If auditd process is not running, you may need to delete anything with auditd 
> in its name in the /var/run directory.
> 
> -Steve
> 

After reboot, there is now nothing in /var/run with audit, or even au in the 
name. The service is stopped, and I cannot start it. Starting just fails.

I noticed that auditd stopped writing to /var/log/audit/audit.log a few hours 
before the log was rotated. Rotation failed. Auditing has since been putting its 
output in /var/log/messages, even though auditd is not running, though "ps aux" 
shows

  root      2242  0.0  0.0     0    0 ?        S<   Apr12   0:00 [kauditd]

I think the problem is that auditd cannot write to the log, but I don't know 
why. The permissions on the log seems to be the same as on other systems I run. 
The directory permission was 700, where it is 750 on other systems, but changing 
it to 750 didn't help.

Any other ideas?

  reply	other threads:[~2007-04-13 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12 14:08 wierd audit problems on one RHEL ES4 box Bill Tangren
2007-04-12 14:14 ` Steve Grubb
2007-04-13 14:27   ` Bill Tangren [this message]
2007-04-13 14:30     ` Steve Grubb
2007-04-13 14:37     ` Kirkwood, David A.
2007-04-13 14:54       ` Bill Tangren

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=461F9335.9040205@usno.navy.mil \
    --to=bjt@usno.navy.mil \
    --cc=linux-audit@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 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.