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]
>> >> $
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
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 j
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
[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 mo
