Bug 1462615
Summary: | Default installation does not report on systemd services requiring journalctl access to their logs | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ivor Durham <ivor.durham> |
Component: | logwatch | Assignee: | Jan Synacek <jsynacek> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 27 | CC: | frank, gbcox, goeran, herrold, jsynacek, varekova |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-11-30 21:38:33 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: |
Description
Ivor Durham
2017-06-19 05:29:48 UTC
Changing to F26 because this still isn't fixed. I had to do a clean install of F25 Workstation and am not getting any output at all from Logwatch, even after the above changes (In reply to Gerald Cox from comment #1) > Changing to F26 because this still isn't fixed. > I had to do a clean install of F25 Workstation and am not getting any output > at all from Logwatch, even after the above changes Try "sudo logwatch --debug 100" to see if the debugging output gives you any insight. You shouldn't use the "--output=cat" option, should you? That removes the time stamp and process name from the output lines, parts that at least some logwatch patterns look for. I have tried to do this on some of my systems, and it seems to work. For example, my /etc/logwatch/conf/logfiles/cron.conf looks like this: LogFile = LogFile = /etc/logwatch/conf/empty *JournalCtl = "--no-pager --unit=crond.service" *RemoveService = anacron (In reply to Ivor Durham from comment #2) > (In reply to Gerald Cox from comment #1) > > Changing to F26 because this still isn't fixed. > > I had to do a clean install of F25 Workstation and am not getting any output > > at all from Logwatch, even after the above changes > > Try "sudo logwatch --debug 100" to see if the debugging output gives you any > insight. I updated: https://bugzilla.redhat.com/show_bug.cgi?id=864872 with more information. The good people over at the Arch distro seem to have a good handle on it. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. hold against age out This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |