Comment # 20 on bug 1229721 from Andrei Borzenkov

(In reply to Stefan Seyfried from comment #16)
> Created attachment 877075 [details]
> journalctl -b with systemd.log_level=debug udev.log_level=info
> 
> This one seems less truncated :-)

```
Aug 31 21:43:33 mixi journalctl[1125]: varlink: Setting state idle-client
Aug 31 21:43:33 mixi journalctl[1125]: journal: Sending message:
{"method":"io.systemd.Journal.FlushToVar","parameters":{}}
Aug 31 21:43:33 mixi journalctl[1125]: journal: Changing state idle-client →
calling
Aug 31 21:43:33 mixi journalctl[1125]: journal: Received message:
{"parameters":{}}
Aug 31 21:43:33 mixi journalctl[1125]: journal: Changing state calling → called
Aug 31 21:43:33 mixi journalctl[1125]: journal: Changing state called →
idle-client
Aug 31 21:43:33 mixi journalctl[1125]: journal: Changing state idle-client →
disconnected
```

What shows

lsof /run/systemd/journal/io.systemd.journal


Does /run/systemd/journal/flushed exist? If not, what happens if you manually
call

journalctl --flush