rsyslogd crashes from time to time due to memory corruption

Solution Verified - Updated -

Issue

  • The system journal shows that rsyslogd crashes from time to time due to memory corruption (SEGV or ABRT signals), as shown in the example below

    # journalctl -u rsyslog | grep "code=killed"
May 03 09:31:10 HOSTNAME systemd[1]: rsyslog.service: Main process exited, code=killed, status=11/SEGV
May 03 11:52:38 HOSTNAME systemd[1]: rsyslog.service: Main process exited, code=killed, status=11/SEGV
May 03 12:29:27 HOSTNAME systemd[1]: rsyslog.service: Main process exited, code=killed, status=11/SEGV
May 03 12:38:05 HOSTNAME systemd[1]: rsyslog.service: Main process exited, code=killed, status=6/ABRT
May 03 13:14:54 HOSTNAME systemd[1]: rsyslog.service: Main process exited, code=killed, status=11/SEGV

Environment

  • Red Hat Enterprise Linux 7 and later
    • rsyslog configured to forward messages to multiple destinations

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