<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 --- - systemd-journald - 60 second pause in dracut, then hangs systemd at Init Default Target"
href="https://bugs.freedesktop.org/show_bug.cgi?id=71721">71721</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>systemd-journald - 60 second pause in dracut, then hangs systemd at Init Default Target
</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>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>james@nurealm.net
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86 (IA32)
</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>Arch Linux
kernel 3.12.0-1-ARCH
dracut 034-1
systemd 208-2
Symptom: on boot with "systemd.log_level=debug", after log message"Started
Journal Service", the booting-process pauses for exactly 60 seconds. Then, at
Init Default Target, after pivot, where systemd proper should start, after the
log message "systemd-journald[43]: Received SIGTERM", the system hangs
permanantly.
Circumstances: The pause and hang can be influenced by the "debug" and
"systemd.log_target=<blah>" kernel command-line boot parameters.
With no "debug" and no "systemd.log_target=<blah>" parameter, the boot pauses
and then hangs.
With "debug" and no "systemd.log_target=<blah>" parameter, the boot never
pauses or hangs and seems to start normally.
With no "debug" and with any of
"systemd.log_target=[journal|syslog|journal-or-kmsg|syslog-or-kmsg]", the boot
will pause and then hang.
With no "debug" and with any of "systemd.log_target=[console|kmsg|null]", the
boot does not pause or hang and seems to start normally.
The pause and hang seem to be related to systemd-journald. Setting "debug" or
setting "systemd.log_target=[console|kmsg|null]" acts as a work-around to the
pause and hang.
With no "debug" and no "systemd.log_target=<blah>" parameter, where the boot
would otherwise pause and then hang, using the kernel command-line boot
parameter "init=/usr/bin/bash", the shell starts normally, and then running
"/usr/lib/systemd/systemd --system" from the shell, all systemd-managed
processes seem to start-up normally.
Hopefully, that's enough information to narrow-down the source of the problem.
Let me know if there is any easy way to expose more useful error messages
during the pause or at the hang.</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>