On Mo, 11.10.21 10:57, Ulrich Windl (Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx) wrote: > > Now when journald hangs due to some underlying IO issue, then it might > > miss the watchdog deadline, and PID 1 might then kill it to get it > > back up. It will log about this to the journal, but given tha tthe > > journal is hanging/being killed it's not going to write the messages > > to disk, the mesages will remain queued in the logging socket for a > > bit. Until eventually journald starts up again, and resumes processing > > log messages. it will then process the messages already queued in the > > sockets from when it was hanging, and thus the order might be > > surprising. > > Hi! > > Thanks for explaining. > Don't you have some OOB-logging, that is: Log a message before processing the > queue logs. The "Journal started" message is inserted into the log stream by journald itself before processing the already queued messages. Lennart -- Lennart Poettering, Berlin