rsyslog crashes on segfault when disk-assisted queues are corrupted

Solution Verified - Updated -

Issue

  • rsyslog segfaults at startup, and systemd restarts it loop forever

    # systemctl start rsyslog
    Job for rsyslog.service failed because a fatal signal was delivered to the control process. See "systemctl status rsyslog.service" and "journalctl -xe" for details.
    
    # journalctl | grep rsyslog
    <TIMESTAMP> <hostname> systemd[1]: rsyslog.service holdoff time over, scheduling restart.
    <TIMESTAMP> <hostname> systemd[1]: rsyslog.service: main process exited, code=killed, status=11/SEGV
    <TIMESTAMP> <hostname> systemd[1]: Unit rsyslog.service entered failed state.
    <TIMESTAMP> <hostname> systemd[1]: rsyslog.service failed.
    <TIMESTAMP> <hostname> systemd[1]: rsyslog.service holdoff time over, scheduling restart.
    <TIMESTAMP> <hostname> systemd[1]: rsyslog.service: main process exited, code=killed, status=11/SEGV
    <TIMESTAMP> <hostname> systemd[1]: Unit rsyslog.service entered failed state.
    
  • rsyslog shows this message in debug mode on stderr

    <Obj:1:msg:1:
    +iProtocolVersion:2:1:0:
    +iSeverity:2:1:5:
    +iFacility:2:2:16:
    +m'
    3817.443895127:action 0 queue[DA]:Reg/w0: error property name: 'iFacilit<Obj'
    3817.443898262:action 0 queue[DA]:Reg/w0: error var type: '1'
    Segmentation fault
    
  • The following message is seen in the journal

    <TIMESTAMP> <hostname> kernel: rs:action 0 que[29724]: segfault at 5 ip 0000558247132cec sp 00007f75b3cbfb50 error 4 in rsyslogd[55824710c000+95000]
    

Environment

  • Red Hat Enterprise Linux 7
  • rsyslog

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