From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Audit logs rotation problem
Date: Tue, 22 May 2012 10:58:26 -0400 [thread overview]
Message-ID: <201205221058.26810.sgrubb@redhat.com> (raw)
In-Reply-To: <17de8d52f1c5c3f9bad49089a4a7c69f@192.168.210.10>
On Monday, May 21, 2012 09:11:51 AM Nicolas GORALSKI wrote:
> Hi all
>
> I've a got a problem on my audit log rotation.
>
> Because we've got a lot of logs on our server (a little bit of rules
> and lot of activities), we've decided to rotate logs every hours to
> compress, backup and delete them.
> I'm using the command "/etc/init.d/auditd rotate" to rotate them, no
> other commands.
>
> By the way we have some errors, sometimes logs are rotated twice.
>
> The rotation job was successful and we have as a result this
> compressed file :
> audit_20120507-0940--20120507-1040.log.gz
>
> The file contain in the firts line this information about the previous
> rotation at 9h40
> type=DAEMON_ROTATE msg=audit(1336376401.094:8139): auditd sending
> auid=0 pid=20084 subj=root:system_r:initrc_t:s0
>
> But we have a second file created a few seconds after the previous one
> named : audit_20120507-1040--20120507-1040.log.gz
>
> The first line contain this text :
> type=DAEMON_ROTATE msg=audit(1336380001.723:8140): auditd error
> getting usr1 info - no change, sending auid=? pid=? subj=? res=failed
Whenever a signal comes in for log rotation, the audit system needs to find out
who asked for it. So, it queries the kernel. In this case its saying it couldn't
figure out who asked for the rotation - which is unusual. This almost looks like
2 signals came in or something to that effect.
-Steve
next prev parent reply other threads:[~2012-05-22 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 13:11 Audit logs rotation problem Nicolas GORALSKI
2012-05-22 14:58 ` Steve Grubb [this message]
2012-05-23 13:37 ` Nicolas GORALSKI
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=201205221058.26810.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--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.