<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - journalctl mixes new logs with logs from the previous boot on crash (no RTC)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64760">64760</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>journalctl mixes new logs with logs from the previous boot on crash (no RTC)
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>lekensteyn@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr></table>
<p>
<div>
<pre>Originally mentioned at <a class="bz_bug_link
bz_status_CLOSED bz_closed"
title="CLOSED FIXED - All logs since last boot gone after crash/hard reboot"
href="show_bug.cgi?id=61411#c9">https://bugs.freedesktop.org/show_bug.cgi?id=61411#c9</a>:
--->8--->8--->8--->8--->8--->8--->8--->8--->8--->8--->8---
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.
---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---
This corruption occurs when the system is uncleanly shut down (pull power). It
makes logs hard to read with journalctl.
These logs are taken from a Raspberry Pi, an ARM board with no RTC.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>