Thanks Am 05.05.2018 um 05:27 schrieb Marc Lehmann:
> #4 0x00007fffeffbfe13 in generic_array_bisect (f=f@entry=0x55555557ad10,
> first=<optimized out>, first@entry=3739384, n=n@entry=2343, needle=11772088,
> test_object=0x7fffeffbe100 <test_object_offset>,
> direction=direction@entry=DIRECTION_UP, ret=0x0, offset=0x7fffffffdbd0,
> idx=0x0) at ../src/journal/journal-file.c:2019
> 2019 in ../src/journal/journal-file.c
> (gdb) p *f
> $1 = {
> fd = 13,
> mode = 0,
> flags = 0,
> prot = 1,
> writable = false,
> compress_xz = false,
> compress_lz4 = true,
> seal = false,
> defrag_on_close = false,
> close_fd = true,
> archive = false,
> tail_entry_monotonic_valid = false,
> last_direction = DIRECTION_UP,
> location_type = LOCATION_HEAD,
> last_n_entries = 8977,
> path = 0x55555557aef0
> "/var/log/journal/a1002e4c6eb50c7b5cdd5e004698a90b/system@7ea033a201334367b130dd1201659ee1-00000000007a33f3-00056a7eb6600ac0.journal",
>
What does journalctl --verify say about this particular 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?
Can you reproduce the problem with systemd v238 from sid/buster?
In case you don't want to upgrade your system to buster for this:
it should be possible to point journalctl from a v238 installation at
the journal files of your stetch system via journalctl --directory.
Are you able able/willing to share the journal file(s)?
At some point we will probably have to involve upstream, at least if the
problem is still reproducible with v238.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
