Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
While reproducing BZ https://bugzilla.redhat.com/show_bug.cgi?id=1509987 I found that after the above issue with rsyslog happened, one could not send any logs further to systemd-journald.
A strace of "logger" shows the following:
# strace logger '{ "key": "value" }'
execve("/usr/bin/logger", ["logger", "{ \"key\": \"value\" }"], [/* 26 vars */]) = 0
...
socket(AF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3
connect(3, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = -1 ECONNREFUSED (Connection refused)
close(3) = 0
=> ECONNREFUSED
Version-Release number of selected component (if applicable):
systemd-219-42.el7_4.4.x86_64
How reproducible:
Always
Steps to Reproduce: use reproducer of BZ https://bugzilla.redhat.com/show_bug.cgi?id=1509987
1. Install rsyslog-mmjsonparse package
# yum -y install rsyslog-mmjsonparse
2. Configure mmjsonparse
# cat /etc/rsyslog.d/json.conf
module(load="mmjsonparse") # Load mmjsonparse module for structured logs
action(type="mmjsonparse" cookie='')
if $parsesuccess == "OK" then {
action(type="omfile" File="/tmp/output")
} else if $parsesuccess == "FAIL" then {
action(type="omfile" File="/tmp/parsing_failure")
}
3. Restart rsyslog
# systemctl restart rsyslog
4. Rsyslog will die immediately, respin, then systemd will abort respinning
5. Send log using logger
# strace logger Test
Actual results:
connect(3, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = -1 ECONNREFUSED (Connection refused)
Expected results:
Log sent to journal
Additional info:
Restarting systemd (systemctl daemon-reexec) or restarting systemd-journald doesn't help.
I have to reboot the system to have logs work again (after fixing the rsyslog configuration issue).