Why does auditd use 100% CPU after log rotation?

Solution Verified - Updated -

Issue

The auditd daemon uses high amount (100%) of CPU time after each log rotation, even though the internal log rotation of auditd was disabled by setting num_logs = 0 and max_log_file_action = IGNORE in /etc/audit/auditd.conf.

Environment

  • Red Hat Enterprise Linux 6
  • Red Hat Enterprise Linux 7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content