Sorry for the late reply, I got a bit swamped with work.
On Sat, May 05, 2018 at 12:13:35PM +0200, Michael Biebl <bi...@debian.org>
wrote:
> What does journalctl --verify say about this particular file?
AFAICR, it complained about file corruption for that file.
> Could you create a /var/log/journal-broken directory and move the broken
> journal files away into this directory one by one and test which of the
> files is triggering the abort?
I could when I originally read your reply, but since I was busy at the
time and thought I read somewhere that systemd would leave corrupted
journal files alone, I moved my investigation to later. When I looked for
it now, it was gone.
What I found interesting, though, is that jorunalctl --verify reports file
corruptiopn for a lot of files in /var/log/journal, although I didn't have
a crash (all files are newer than 14 days, and the machine has an uptime
of 40 days and even systemd-journald is running uninterrupted).
> Can you reproduce the problem with systemd v238 from sid/buster?
Wasn't able to test it before it was deleted, sorry. This was unexpected.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schm...@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
