Rsyslog encounters a segfault with "kernel: in:imjournal[####]: segfault at 0 <snip> error 4 in[<addr>]" visible in the logs

Solution Verified - Updated -


  • The rsyslog daemon keeps encountering segfaults in the imjournal plugin. The following is the backtrace visible within the application core file:
    #0  loadJournalState () at imjournal.c:560
    #1  0x00007f5949f142dc in pollJournal () at imjournal.c:511
    #2  runInput (pThrd=<optimized out>) at imjournal.c:678
    #3  0x000055836c91bd94 in thrdStarter (arg=0x55836d206bf0) at ../threads.c:226
    #4  0x00007f594b525e25 in start_thread (arg=0x7f594742d700) at pthread_create.c:308
    #5  0x00007f594a61e34d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113


  • Red Hat Enterprise Linux 7
    • rsyslog-8.24.0-12.el7

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