<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 - boot hangs due to non-starting systemd-journal-flush.service"
href="https://bugs.freedesktop.org/show_bug.cgi?id=85871">85871</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>boot hangs due to non-starting systemd-journal-flush.service
</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>critical
</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>evangelos@foutrelis.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>systemd 217 patched with 919699e (units: don't order journal flushing afte
remote-fs.target) will usually fail to boot and get stuck showing:
"A start job is running for Trigger Flushing of Journal to Persistent Storage"
I haven't been able to reproduce this with systemd.log_level=debug, so I'm not
sure what's going on exactly.
Relevant log entries are:
====================
Nov 04 20:32:04 notbad systemd[1]: Starting Journal Service...
Nov 04 20:32:04 notbad systemd[1]: Started Journal Service.
Nov 04 20:32:04 notbad systemd[1]: Unit systemd-journald.service entered failed
state.
Nov 04 20:32:04 notbad systemd[1]: systemd-journald.service failed.
Nov 04 20:32:04 notbad systemd[1]: systemd-journald.service has no holdoff
time, scheduling restart.
Nov 04 20:32:04 notbad systemd[1]: Stopping Journal Service...
Nov 04 20:32:04 notbad systemd[1]: Starting Journal Service...
Nov 04 20:32:04 notbad systemd[1]: Started Journal Service.
Nov 04 20:32:04 notbad systemd-journal[131]: Journal started
Nov 04 20:32:04 notbad systemd[1]: Starting Trigger Flushing of Journal to
Persistent Storage...
====================
systemd-journald.service didn't fail like that before commit 919699e.
I've also tried adding "After=systemd-remount-fs.service" to the flush service
similar to commit 1f1926a (units: order sd-journal-flush after sd-remount-fs)
but the issue remains.
I'm using Arch Linux although the same issue has been reported on Fedora.
[1][2]
[1] <a href="https://plus.google.com/104174679492403594632/posts/GJ566nR6eUq">https://plus.google.com/104174679492403594632/posts/GJ566nR6eUq</a>
[2] <a href="https://bugs.archlinux.org/task/42678">https://bugs.archlinux.org/task/42678</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>