Re: journald deleting logs on LiveOS boots

[Chris Murphy <lists@xxxxxxxxxxxxxxxxx>]

On Sun, Jul 21, 2019 at 11:48 PM Ulrich Windl
<Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> >>> Chris Murphy <lists@xxxxxxxxxxxxxxxxx> schrieb am 18.07.2019 um 17:55 in
> Nachricht
> <CAJCQCtSioWXDsVScyAdAKjotieT3Gc5dEactOBMUa=15j1SeaQ@xxxxxxxxxxxxxx>:
> > On Thu, Jul 18, 2019 at 4:50 AM Uoti Urpala <uoti.urpala@xxxxxxxxxxx> wrote:
> >>
> >> On Mon, 2019-07-15 at 14:32 -0600, Chris Murphy wrote:
> >> > So far nothing I've tried gets me access to information that would
> >> > give a hint why systemd-journald thinks there's no free space and yet
> >> > it still decides to create a single 8MB system journal, which then
> >> > almost immediately gets deleted, including all the evidence up to that
> >> > point.
> >>
> >> Run journald under strace and check the results of the system calls
> >> used to query space? (One way to run it under strace would be to change
> >> the unit file to use "strace -D -o /run/output systemd-journald" as the
> >> process to start.)
> >
> > It's a good idea but strace isn't available on Fedora live media. So I
> > either have to learn how to create a custom live media locally (it's a
> > really complicated process) or convince Fedora to add strace to live
> > media...
>
> Wouldn't it be easer to scp the binary from a compatible system?

What binary? The problem with the strace idea is that /run/output is 0
length. There's nothing to scp. For whatever reason strace creates
/run/output but isn't writing anything to it. But based on this PR it
looks like some aspect of this problem is understood by systemd
developers.

https://github.com/systemd/systemd/pull/13120


-- 
Chris Murphy
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel