Re: [systemd-devel] journalctl --list-boots fails

[Chris Murphy]

On Wed, Oct 14, 2015 at 10:34 AM, Lennart Poettering
 wrote:
> On Wed, 14.10.15 18:18, Lars Noschinski (nosch...@in.tum.de) wrote:
>
>> On 14.10.2015 17:33, Lennart Poettering wrote:
>> > On Thu, 08.10.15 13:04, Lars Noschinski (nosch...@in.tum.de) wrote:
>> >> [please CC me on answers]
>> >> $ sudo journalctl --list-boots
>> >> Failed to determine boots: No data available
>> [...]
>> > Any chance you can provide us with the precise set of journal files
>> > you have when this happens, so that I can reproduce this here? If you
>> > don't want to put this onine, feel free to send this to me
>> > personally.
>>
>> Which files do you need, everything under /var/log/journal? Does it make
>> sense if I try to minimize this set of files?
>
> Well, sure, I don't really care about the complete set, but only only
> *a* set where you get the error you mention above. The smaller more
> minimal it is, the better, of course. As long as it results in the
> error above...

Resurrecting this thread. I've filed a bug with attached minimal
journal files that reproduce it. It's actually a complete set of
journals, nothing thinned out. It was relatively new, but then I had a
crash and now journalctl -b-1 says it failed to look up boot and that
there's no such boot ID in journal. And yet --list-boots lists what
I'm after including an ID.

https://bugzilla.redhat.com/show_bug.cgi?id=1294002


---
Chris Murphy
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] journalctl --list-boots fails

[Lars Noschinski]

On 14.10.2015 17:33, Lennart Poettering wrote:
> On Thu, 08.10.15 13:04, Lars Noschinski (nosch...@in.tum.de) wrote:
>> [please CC me on answers]
>> $ sudo journalctl --list-boots
>> Failed to determine boots: No data available
[...]
> Any chance you can provide us with the precise set of journal files
> you have when this happens, so that I can reproduce this here? If you
> don't want to put this onine, feel free to send this to me
> personally.

Which files do you need, everything under /var/log/journal? Does it make
sense if I try to minimize this set of files?

  -- Lars
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] journalctl --list-boots fails

[Lennart Poettering]

On Thu, 08.10.15 13:04, Lars Noschinski (nosch...@in.tum.de) wrote:

> [please CC me on answers]
> 
> Hi,
> 
> today I had to deal with my machine crashing a lot. This seems to have
> corrupted some journal data, as journalctl cannot lists the boots anymore:
> 
> $ sudo journalctl --list-boots
> Failed to determine boots: No data available
> 
> It was working fine earlier this morning. The log data itself seems to
> be still readable (that is, "journalctl -b-" gives plausible
> results). What can I do to to fix this issue?

Any chance you can provide us with the precise set of journal files
you have when this happens, so that I can reproduce this here? If you
don't want to put this onine, feel free to send this to me
personally.

I figure I really need to look at the files in order to track this down.

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] journalctl --list-boots fails

[Lennart Poettering]

On Wed, 14.10.15 18:18, Lars Noschinski (nosch...@in.tum.de) wrote:

> On 14.10.2015 17:33, Lennart Poettering wrote:
> > On Thu, 08.10.15 13:04, Lars Noschinski (nosch...@in.tum.de) wrote:
> >> [please CC me on answers]
> >> $ sudo journalctl --list-boots
> >> Failed to determine boots: No data available
> [...]
> > Any chance you can provide us with the precise set of journal files
> > you have when this happens, so that I can reproduce this here? If you
> > don't want to put this onine, feel free to send this to me
> > personally.
> 
> Which files do you need, everything under /var/log/journal? Does it make
> sense if I try to minimize this set of files?

Well, sure, I don't really care about the complete set, but only only
*a* set where you get the error you mention above. The smaller more
minimal it is, the better, of course. As long as it results in the
error above...

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] journalctl --list-boots fails

[Lars Noschinski]

[please CC me on answers]

Hi,

today I had to deal with my machine crashing a lot. This seems to have
corrupted some journal data, as journalctl cannot lists the boots anymore:

$ sudo journalctl --list-boots
Failed to determine boots: No data available

It was working fine earlier this morning. The log data itself seems to
be still readable (that is, "journalctl -b-" gives plausible
results). What can I do to to fix this issue?

This is is systemd 226 from Debian.

  -- Lars

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel