Bug 1545580
| Summary: | rsyslog appears to duplicate messages from journald when journald rotates its log files [rhel-7.4.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | rsyslog | Assignee: | Jiří Vymazal <jvymazal> |
| Status: | CLOSED ERRATA | QA Contact: | Dalibor Pospíšil <dapospis> |
| Severity: | high | Docs Contact: | Ioanna Gkioka <igkioka> |
| Priority: | urgent | ||
| Version: | 7.4 | CC: | bbreard, bleanhar, cww, dapospis, dkopecek, fkrska, igkioka, jvymazal, lmiksik, mgrepl, mthacker, nkinder, pportant, rmeggins, rmetrich, sdordevi, stwalter, xuliu |
| Target Milestone: | rc | Keywords: | Patch, Reopened, Triaged, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | rsyslog-8.24.0-12.el7_4.6 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, when the journal was rotated, a bug in the rsyslog system caused certain log messages to appear twice in the output. This bug has been fixed, and rsyslog no longer displays duplicate messages.
|
Story Points: | --- |
| Clone Of: | 1538372 | Environment: | |
| Last Closed: | 2018-04-17 16:38:08 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1538372 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-02-15 10:12:36 UTC
Close to merge is a matter of opinion? Has this been verified to perform or satisfy the customer case? Are we really going to release a patch to a customer that will then have a different solution upstream? Seems like a really bad idea, no? (In reply to Peter Portante from comment #24) > Close to merge is a matter of opinion? Has this been verified to perform or > satisfy the customer case? Are we really going to release a patch to a > customer that will then have a different solution upstream? Seems like a > really bad idea, no? Only customer issues I am aware of are the duplication of logs upon journal rotation and possible regression when changing journal config on-the-fly and both are verified as resolved with current build, so unless you have some other inputs we are going to release it. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1152 |