Red Hat Bugzilla – Bug 866278
journalctl: Failed to iterate through journal: Bad message
Last modified: 2013-08-01 07:25:59 EDT
Description of problem:
journalctl prints log messages just fine, but if I try to filter the output in some way, I get this output:
#> journalctl _COMM=setroubleshootd
Logs begin at Sun, 27 May 2012 14:09:45 -0700, end at Tue, 25 Sep 2012 23:52:17 -0700.
Failed to iterate through journal: Bad message
It makes no difference how I try filtering the message; some apparent corruption on 25 Sep prevents it from working.
Here is the only message on Septermber 25 courtesy of journalctl --no-pager -o verbose:
Tue, 25 Sep 2012 23:52:17 -0700 [s=c54ec7782b8e4d49a4c8b531a1cae7e2;i=365d3;b=8087e23ce0d448e095004338f3770e04;m=2c9de9dd;t=4ca954372a69a;x=a9f4251302ffd007;p=user-42.journal]
MESSAGE=Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
This doesn't look any different from any of the messages that precede or follow it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. You probably won't be able to reproduce it on your system unless you can intentionally corrupt the logs somehow
This is the only other possibly related bug I could find while googling: https://bugzilla.novell.com/show_bug.cgi?id=779449
I'm not sure how to debug this further or what I can do to help; just let me know what you need and I will try my best
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora
'version' of '17'.
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 prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.
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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.
Thank you for reporting this bug and we are sorry it could not be fixed.