<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-networkd: hang writing journal entry (v215)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=81628">81628</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>systemd-networkd: hang writing journal entry (v215)
</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>brandon@ifup.co
</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>We have a service that writes to the systemd socket using
github.com/coreos/go-systemd. With systemd 215 we have noticed that on some
boots the process will hang trying to write to the socket. At around the same
time that this process is starting journald is doing a compaction.
I will try and gather more details; it is a very easy thing to reproduce.
Jul 22 02:31:22 localhost systemd-journal[87]: Runtime journal is using 6.2M
(max allowed 49.9M, trying to leave 74.8M free of 492.8M available → current
limit 49.9M).
Jul 22 02:31:22 localhost systemd-journal[87]: Runtime journal is using 6.2M
(max allowed 49.9M, trying to leave 74.8M free of 492.8M available → current
limit 49.9M).
Jul 22 02:31:22 localhost systemd-journal[87]: Journal started
Jul 22 02:31:22 localhost systemd-journal[87]: Missed 73 kernel messages
Jul 22 02:31:22 localhost systemd-journal[87]: Missed 0 kernel messages
Jul 22 02:31:22 localhost systemd-journal[87]: Missed 5 kernel messages
Jul 22 02:31:22 localhost systemd-journal[87]: Missed 0 kernel messages
Jul 22 02:31:23 localhost systemd-journal[87]: Missed 0 kernel messages
Jul 22 02:31:23 localhost systemd-journal[87]: Missed 7 kernel messages
Jul 22 02:31:23 localhost systemd-journal[87]: Missed 1 kernel messages
Jul 22 02:31:23 localhost systemd-journal[87]: Missed 1 kernel messages
Jul 22 02:31:24 localhost systemd-journal[87]: Missed 11 kernel messages
Jul 22 02:31:24 core-03 systemd-journal[369]: Runtime journal is using 6.2M
(max allowed 49.9M, trying to leave 74.8M free of 486.6M available → current
limit 49.9M).
Jul 22 02:31:24 core-03 systemd-journal[369]: Runtime journal is using 6.2M
(max allowed 49.9M, trying to leave 74.8M free of 486.6M available → current
limit 49.9M).
Jul 22 02:31:24 core-03 systemd-journal[369]: Journal started
Jul 22 02:31:25 core-03 systemd-journal[369]: Permanent journal is using 24.0M
(max allowed 1.6G, trying to leave 2.4G free of 15.7G available → current limit
1.6G).
Jul 22 02:31:25 core-03 systemd-journal[369]: Time spent on flushing to /var is
379.365ms for 820 entries.</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>