<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 - snoopy (LD_PRELOAD logging of exec calls) prevents boot since jounald start times out and is repeated over and over"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90364">90364</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>snoopy (LD_PRELOAD logging of exec calls) prevents boot since jounald start times out and is repeated over and over
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</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>zaphodb@zaphods.net
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>On two instances of Xen "PV on HVM" Servers running Debian that were freshly
dist-upgraded from wheezy to jessie i found that they were unable to boot while
snoopy ( <a href="https://packages.debian.org/jessie/snoopy">https://packages.debian.org/jessie/snoopy</a> ) was enabled. They did
however boot up just fine after snoopy was disabled.
It seems that the logging of all execve calls by snoopy via an LD_PRELOAD
wrapping of that function somehow interferes with the upbringing of journald
and apparently also prevents it from responding to systemd in time so that it
gets restarted over and over without ever succeeding to launch and thus
preventing systemd to continue booting up.
It seems the issue has already been reported at Fedora in
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=745603">https://bugzilla.redhat.com/show_bug.cgi?id=745603</a> .
I realize that this might not be exactly the fault of systemd but rather of the
crude way that snoopy is implemented however maybe you can think of an elegant
way to work around the issue.
Sadly i was unable to produce any more detailed output by setting
ForwardToConsole=yes TTYPath=/dev/ttyS0 (i also tried /dev/console) in
/etc/systemd/journald.conf .
Console looked like this booting up while snoopy was enabled:
[ OK ] Stopped Trigger Flushing of Journal to Persistent Storage.
Stopping Journal Service...
[ OK ] Stopped Journal Service.
Starting Journal Service...
[ OK ] Started Journal Service.
[*** ] (4 of 5) A start job is running for LSB: Set keymap ... 9s / no
limit)[ 2771.768127] systemd[1]: systemd-journald.service watchdog timeout
(limit 1min)!
Starting Journal Service...
[ OK ] Stopped Trigger Flushing of Journal to Persistent Storage.
Stopping Journal Service...
[ OK ] Stopped Journal Service.
Starting Journal Service...
[ OK ] Started Journal Service.
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
Stopping udev Kernel Device Manager...
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[ ***] (3 of 5) A start job is running for Apply Kernel Var... 9s / no
limit)[ 2832.004137] systemd[1]: systemd-journald.service watchdog timeout
(limit 1min)!
Starting Journal Service...
[ OK ] Stopped Trigger Flushing of Journal to Persistent Storage.
Stopping Journal Service...
[ OK ] Stopped Journal Service.
Starting Journal Service...
[ OK ] Started Journal Service.
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
Stopping udev Kernel Device Manager...
[ OK ] Stopped udev Kernel Device Manager.
Starting udev Kernel Device Manager...
[ 2892.256176] systemd[1]: systemd-journald.service watchdog timeout (limit
1min)!
Starting Journal Service...
[ OK ] Stopped Trigger Flushing of Journal to Persistent Storage.
Stopping Journal Service...
[ OK ] Stopped Journal Service.
Starting Journal Service...
[ OK ] Started Journal Service.</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>