Red Hat Bugzilla – Bug 836485
rsyslogd segfaults when this config file is used
Last modified: 2014-06-18 03:51:52 EDT
Description of problem:
I'm not sure which of the last 9 lines in the config file causes the segfault, but one of them is definitely the culprit.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
# grep -v -e '^#' -e '^$' /etc/rsyslog.conf
$ModLoad imuxsock # provides support for local system logging (e.g. via logger command)
$ModLoad imklog # provides kernel logging support (previously done by rklogd)
# service rsyslog restart
Redirecting to /bin/systemctl restart rsyslog.service
# service rsyslog status
Redirecting to /bin/systemctl status rsyslog.service
rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled)
Active: failed (Result: signal) since Fri, 29 Jun 2012 10:27:42 +0200; 2s ago
Process: 32134 ExecStart=/sbin/rsyslogd -n $SYSLOGD_OPTIONS (code=killed, signal=SEGV)
Process: 32131 ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service (code=exited, status=0/SUCCESS)
* rsyslogd is not running
* rsyslogd is running
Following line was missing in the confi file:
When this line is present the service does not segfault anymore.
I'm going to correct the automated test.
This was fixed in the upstream version 7.4.5. The current version in el7 is 7.4.2 but a rebase is planned which would resolve this issue.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.