Bug 1426152
Summary: | Journalctl miss to show logs from unit | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Davide Lima "Duarte" Daum <infinity.sbn> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 24 | CC: | johannbg, lnykryn, msekleta, muadda, peter, ssahani, s, systemd-maint, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-02-24 08:24:24 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
Davide Lima "Duarte" Daum
2017-02-23 10:09:10 UTC
This is a known issue. systemd-journald sometimes fails to record information about unit from which log message originates. There is a higher probability of hitting this problem if the process that logs the message is short lived. So in the end the old, This is not a good thing, the logs can not disappear in this way. In addition, the denied possibility to return to the good old *syslog makes it quite ridiculous... This is not a good thing, the logs can not disappear in this way. In addition, the denied possibility to return to the good old *syslog makes it quite ridiculous... Logs are not disappearing anywhere. It's just that for some log messages that originate from short lived processes journald can't figure out respective cgroup (unit). Thus you will not see those log lines if you apply filtering based on unit name. We can't do anything about this until kernel gives us a way to gather cgroup information in non racy way. But then again, logs are there and your first command that uses time based filtering proves that. Since this is a "known issue", I'd like to know if we could be pointed to an issue filed against the kernel for this in https://bugzilla.kernel.org/ ? Peter See the other bugs for multiple patch submission attempts. *** This bug has been marked as a duplicate of bug 963620 *** |