<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - (tmpfiles,journald) systemd 219-6 + linux 4.0.1-1 = journal failing to append on boot"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90268">90268</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>(tmpfiles,journald) systemd 219-6 + linux 4.0.1-1 = journal failing to append on boot
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>brent.saner@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>in some cases (i can't seem to narrow down which yet), systemd fails to create
/run/log/journal. This then causes further failure of journald to fail to both:
-append to the volatile journal
-append to the persistent journal (if one exists)- no flushes, as the volatile
journal is not appended
from what i understand, the volatile journal does not exist because it normally
is written to /run/log/journal. on boot, the entries of /run/log/journal are
copied over to the persistent journal in /var/log/journal/ (if persistence is
enabled) (is this correct?).
this is occurring on fully updated/patched Arch Linux, x86_64.
this behaviour does not exist on kernel 3.19.3.
of three machines with systemd, i note the following:
machineA (desktop): does not create /run/log/journal; no new journal entries
are created.
machineB (laptop): does not create /run/log/journal; HOWEVER, new journal
entries SEEM to be appended/created.
machineC (firewall box): /run/log/journal IS created; new journal entries are
added.
machineA and machineB share the exact same /etc/systemd/journald.conf (with no
syslog):
[bts@workhorse systemd]$ egrep -Ev '^[[:space:]]*(#|$)' journald.conf
[Journal]
Storage=persistent
Compress=yes
SystemMaxUse=100M
SystemMaxFileSize=20M
machineC, however, uses no persistence and uses a purely volatile journal (with
syslog):
[root@comptroller systemd]# egrep -Ev '^[[:space:]]*(#|$)' journald.conf
[Journal]
Storage=volatile
Seal=no
SystemMaxUse=50M
RuntimeMaxUse=50M
ForwardToSyslog=yes
as a temporary workaround, it seems that "systemctl restart systemd-journald"
on the affected machine (machineA) seems to allow new journal entries. however,
/run/log/journal is still not created during the restart.
let me know what logs/output/etc. you wish to see.
(cross-linking for reference: <a href="https://bugs.archlinux.org/task/44799">https://bugs.archlinux.org/task/44799</a> )</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>