Rsyslog crashes in SanitizeMsg on start

Solution Verified - Updated -

Issue

  • The rsyslog service does not start
  • The rsyslog service fails and cannot be restarted

  • The rsyslogd crashes on segmentation fault with a message similar to the following visible in the logs:

    kernel: traps: in:imjournal[xxxxx] general protection ip:<addr> sp:<addr> error:0 in libgcc_s-4.8.5-20150702.so.1[<addr>]

Environment

  • Red Hat Enterprise Linux 7
  • rsyslogd with the imjournal input module enabled (the default)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.