<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED FIXED - All logs since last boot gone after crash/hard reboot" href="https://bugs.freedesktop.org/show_bug.cgi?id=61411#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED FIXED - All logs since last boot gone after crash/hard reboot" href="https://bugs.freedesktop.org/show_bug.cgi?id=61411">bug 61411</a> from <a class="email" href="mailto:lekensteyn@gmail.com" title="Peter Wu <lekensteyn@gmail.com>"> Peter Wu</a> <pre>The original issue in this bug (logs gone on crash) is solved. Entries are properly written to the journals. I have a different issue where the order of messages is interleaved (journalctl is apparently sorting by date?), but that fails horribly because there is no RTC in my device. Therefore, all boots starts on January 1st. rsyslogd would write log entries to disk and if power is suddenly gone, you can see the new boot log entries appended to the previous one. rsyslogd example (after reboot, truncated to preserve space): Jan 1 01:00:16 arpi systemd[1]: Starting OpenNTP Daemon... Jan 1 01:00:17 arpi systemd[1]: Failed to read PID from file /run/nginx... Jan 1 01:00:17 arpi systemd[1]: Started A high performance ... May 19 14:32:10 arpi systemd[1]: Time has been changed May 19 14:32:10 arpi systemd[1]: Started OpenNTP Daemon. journalctl (diff on journal before "crash" and after reboot): +Jan 01 01:00:16 arpi systemd[1]: Starting OpenNTP Daemon... +-- Reboot -- (old log entries here) +-- Reboot -- +Jan 01 01:00:17 arpi systemd[1]: Failed to read PID from file /run/nginx... +-- Reboot -- (more old log entries and newer entries interleaved) +May 19 14:31:10 arpi sshd[358]: pam_unix(sshd:session): ... +May 19 14:31:10 arpi systemd-logind[115]: New session c2 ... +-- Reboot -- +May 19 14:32:10 arpi systemd[1]: Time has been changed +May 19 14:32:10 arpi systemd[1]: Started OpenNTP Daemon. Again, this is a completely different issue, I am not sure what it is related to.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>