Ansible Automation Platform 2.5 jobs fail with "The running ansible process received a shutdown signal" due to system hangs from audit backlog limit and security agent activity

Solution Verified - Updated -

Issue

Following an upgrade to AAP 2.5, multiple scheduled and ad-hoc jobs fail concurrently with one or more of the following symptoms:

  • Job Errors:

    • The running ansible process received a shutdown signal.
    • Worker did not produce events or streaming was aborted, check execution node health.
    • Job reaped due to instance shutdown.
  • UI/Platform Symptoms:

    • Automation Controller nodes intermittently toggle between Available and Unavailable in the Web UI.
    • Intermittent 503 Service Unavailable or 403 Forbidden errors when accessing the platform.
    • Database connection errors in tower.log: psycopg.OperationalError: connection failed: server closed the connection unexpectedly.
  • System Logs:

    • /var/log/messages or the serial console shows: audit: backlog limit exceeded.
    • High CPU load spikes and frozen system behavior for 60+ seconds.

Environment

  • Red Hat Ansible Automation Platform (AAP) 2.5
  • Red Hat Enterprise Linux (RHEL) 8 or 9
  • Third-party security agents: Microsoft Defender for Endpoint (MDATP), Trend Micro Deep Security (ds_agent).

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