<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - journalctl boot reporting inconsistent"
href="https://bugs.freedesktop.org/show_bug.cgi?id=66664#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - journalctl boot reporting inconsistent"
href="https://bugs.freedesktop.org/show_bug.cgi?id=66664">bug 66664</a>
from <span class="vcard"><a class="email" href="mailto:hortplumber@gmail.com" title="hortplumber@gmail.com">hortplumber@gmail.com</a>
</span></b>
<pre>I just posted the journalctl diagnostic tool as an attachment.
It should run standalone on most systems with perl ~5.6 or later. All my
local library dependencies were interpolated into the script so hopefully
there should not be any dangling dependencies.
The source contains a reasonably complete documentation header up top. If you
want to understand what the tool does and how it performs the drop-rate
analysis, you'll have to read it. Sorry.
If you simply want to run it in appliance-operator mode and post your results
here to the bug tracker for others to look over then you don't need to
understand much about what it's doing, but you should still read the paragraph
beginning with "jcdiag expects..." which describes the assumptions regarding
the logfile contents. Otherwise the results you post may be meaningless.
To run in appliance-operator mode, just
$ jcdiag -v yourlogfile 2> yourlogfile.err
should do the trick. This will create a report file named yourlogfile.rpt,
and write verbose stderr contents to yourlogfile.err. Post both of those
files to the bugtracker.
Neither file should contain any private information, but check it to be sure
of course. Anything posted to this bugtracker is world-visible.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>