From: Lev Olshvang <levonshe@yandex.com>
To: Steve Grubb <sgrubb@redhat.com>,
"linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: why I have lost messages on boot even with very big backlog while I hunting only 2 syscalls?
Date: Thu, 28 Sep 2017 11:51:38 +0300 [thread overview]
Message-ID: <35811506588698@web59g.yandex.ru> (raw)
In-Reply-To: <3751114.k3uyVqUoiX@x2>
28.09.2017, 00:32, "Steve Grubb" <sgrubb@redhat.com>:
> On Wednesday, September 27, 2017 4:41:29 PM EDT Lev Olshvang wrote:
>> Hello list !
>>
>> A very technical question
>> I have Ubuntu 16.10 Virtual Box , auditd 2.7.8
>> I have audit=1 parameter in grub.cfg
>> I see that /proc/cmdline indeed sees it
>>
>> I see that auditd is started with PID 564
>>
>> root 312 2 0 23:12 ? 00:00:00 [kauditd]
>> root 564 1 0 23:12 ? 00:00:00 /sbin/auditd
>>
>> And I have 15 lost messages ???
>> auditctl -s
>> enabled 1
>> failure 1
>> pid 564
>> rate_limit 0
>> backlog_limit 16384
>> lost 15
>> backlog 0
>> backlog_wait_time 30
>> loginuid_immutable 0 unlocked
>>
>> auditctl -l
>> -a always,exit -F arch=b64 -S execve,execveat -F key=exec
>>
>> Do I understand correctly that auiditd is indeed started by systemd before
>> other services, except 2 that is listed in auditd.service dependencuies -
>> local-fs and some temp setup of systemd ?
>
> Yes, it is started before most services. However. systemd-journal for some
> reason feels obligated to enable auditing. And sometimes people put audit=1 on
> the kernel command line. Either way, auditing is on way before auditd starts.
> The audit logs have a 64 entry buffer by default. So, as the system boots
> events pile up and eventually overflows the 64 entry limit.
>
> The fix is to add another boot command option audit_backlog_limit=8192 or some
> other suitable number. The test to check for this is to boot your system,
> login and run auditctl -s. If you have just booted and lost events during
> boot, this should fix it.
>
> -Steve
Hi Steve
Thank you for your answer.
I added backlog parameter as you advised, but it did not solve the problem
cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.8.0-59-generic root=/dev/mapper/kubuntu--vg-root ro net.ifnames=0 biosdevname=0 audit=1 audit_backlog_limit=8192 debug splash
auditctl -s
enabled 1
failure 1
pid 672
rate_limit 0
backlog_limit 16384
lost 16
backlog 10
backlog_wait_time 30
loginuid_immutable 0 unlocked
Perhaps something else in configuration ?
Ragards,
Lev
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2017-09-28 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 20:41 why I have lost messages on boot even with very big backlog while I hunting only 2 syscalls? Lev Olshvang
2017-09-27 21:32 ` Steve Grubb
2017-09-28 8:51 ` Lev Olshvang [this message]
2017-09-28 14:02 ` Steve Grubb
2017-09-30 12:48 ` Lev Olshvang
2017-09-30 14:03 ` Steve Grubb
2017-10-02 14:16 ` Paul Moore
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=35811506588698@web59g.yandex.ru \
--to=levonshe@yandex.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