Bug 1121253
Summary: | journalctl -b not working (--list-boots absent in manpage but -b is present) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Reartes Guillermo <greartes> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED ERRATA | QA Contact: | Branislav Blaškovič <bblaskov> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.0 | CC: | diego.ml, jchaloup, jscotka, jsynacek, lnykryn, rhack, systemd-maint-list |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | systemd-219-1.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 14:57:03 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
Reartes Guillermo
2014-07-18 19:02:37 UTC
It seems this looks like not a bug as far as systemd is concerned. A simple strace revealed that, it was simply lacking the journal directory. (since we default to 'auto'). Can the manpage be updated to reflect that the directory '/var/log/journal' should exist? for the -b parameter to work. Also the manpage also mentions boot_id, but that will not be avaiable due to the --list-boots parameter not being avaiable. Finally, can the error "Failed to look up boot -1: No se puede asignar la dirección solicitada" be changed somehow? If the os was booted only 10 times with storage auto and the directory '/var/log/journal' is present and i request the logs for the boot -1000, i can understand the previous error. Because there is no such boot. But, if Storage is 'auto' and the directory '/var/log/journal' is absent, can journalctl report that it is not configured to report per boot logs instead? It is not collecting the information necesary for '-b' to work in the first place. "Failed to look up boot -1: functionality not enabled" or something similar. I'm too experiencing this exact same bug with CentOS 7.0: # cat /etc/redhat-release CentOS Linux release 7.0.1406 (Core) I am not sure if this is fixed completely. It would be nice to have a hint that you have only volatile storage, but for now this is best we can do. 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://rhn.redhat.com/errata/RHBA-2015-2092.html |