Bug 1531295
| Summary: | [RFE]: rsyslog imfile support for symlink wildcard combination | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Ruchika K <rkharwar> | |
| Component: | rsyslog | Assignee: | Jiří Vymazal <jvymazal> | |
| Status: | CLOSED ERRATA | QA Contact: | Noriko Hosoi <nhosoi> | |
| Severity: | urgent | Docs Contact: | Mirek Jahoda <mjahoda> | |
| Priority: | urgent | |||
| Version: | 7.4 | CC: | anli, cww, dapospis, dkopecek, jvymazal, ksrot, kwalker, lmiksik, mjahoda, mthacker, nhosoi, pasik, pportant, rkharwar, rmeggins, schituku, tkatarki | |
| Target Milestone: | rc | Keywords: | FutureFeature, Patch, Triaged | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | rsyslog-8.24.0-34.el7 | Doc Type: | Enhancement | |
| Doc Text: |
*rsyslog* `imfile` now supports symlinks
With this update, the *rsyslog* `imfile` module delivers better performance and more configuration options. This enables to use the module for more complicated file monitoring use cases. Users of *rsyslog* are now able to use file monitors with glob patterns anywhere along the configured path and rotate symlink targets with increased data throughput when compared to the previous version.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1563347 1614179 (view as bug list) | Environment: | ||
| Last Closed: | 2018-10-30 10:17:00 UTC | Type: | Bug | |
| 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: | 1601928 | |||
| Bug Blocks: | 1477664, 1563347, 1563409, 1614179 | |||
|
Description
Ruchika K
2018-01-04 23:00:19 UTC
This is the link describing the exact problem: https://github.com/rsyslog/rsyslog/issues/2229 The key to knowing if a fix is working is if rsyslog can be configured along side OCP 3.4 and later to watch /var/log/containers/*.log and see that logs continually flow as those log files are created and deleted (some with the same name as they roll over at the 50 MB limit). The problem is with rsyslog imfile inotify? http://www.rsyslog.com/doc/v8-stable/configuration/modules/imfile.html " mode ["inotify"/"polling"/"fen"] Default: “inotify” Available since: 8.1.5 This specifies if imfile is shall run in inotify (“inotify”) or polling (“polling”) mode. Traditionally, imfile used polling mode, which is much more resource-intense (and slower) than inotify mode. It is suggested that users turn on “polling” mode only if they experience strange problems in inotify mode. In theory, there should never be a reason to enable “polling” mode and later versions will most probably remove it. " Has anyone tried to use `mode polling` as a workaround? I think this qualifies as a "strange" problem. I don't believe polling mode works with wildcards, see: http://www.rsyslog.com/doc/v8-stable/configuration/modules/imfile.html#caveats-known-bugs *** Bug 1563409 has been marked as a duplicate of this bug. *** *** Bug 1563347 has been marked as a duplicate of this bug. *** The imfile work well with the symlink wildcard. input(type="imfile" file="/var/log/containers/*.log" tag="kubernetes" addmetadata="on") rsyslog-8.24.0-34.el7.x86_64 rsyslog-mmjsonparse-8.24.0-34.el7.x86_64 rsyslog-mmnormalize-8.24.0-34.el7.x86_64 rsyslog-elasticsearch-8.24.0-34.el7.x86_64 rsyslog-mmkubernetes-8.24.0-34.el7.x86_64 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/RHEA-2018:3135 |