<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 --- - Service that fails to start gets stuck in respawn loop, spamming logs"
href="https://bugs.freedesktop.org/show_bug.cgi?id=56407">56407</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>Service that fails to start gets stuck in respawn loop, spamming logs
</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>martine@danga.com
</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>systemd 194-4 on Arch.
I screwed up my /etc/groups by accidentally deleting the 'avahi' group, so the
avahi daemon was failing to start. My fault.
The bug is that systemd got into a tight loop of failing to start, spamming the
logs.
Oct 25 09:31:31 kitten avahi-daemon[297]: Failed to find group 'avahi'.
Oct 25 09:32:19 kitten systemd[1]: avahi-daemon.service: main process
exite...55
Oct 25 09:32:19 kitten systemd[1]: Unit avahi-daemon.service entered
failed...e.
Oct 25 10:54:33 kitten avahi-daemon[470]: Failed to find group 'avahi'.
Oct 25 10:54:33 kitten systemd[1]: avahi-daemon.service: main process
exite...55
Oct 25 10:54:33 kitten systemd[1]: Unit avahi-daemon.service entered
failed...e.
Oct 25 10:54:33 kitten avahi-daemon[472]: Failed to find group 'avahi'.
Oct 25 10:54:33 kitten systemd[1]: avahi-daemon.service: main process
exite...55
Oct 25 10:54:33 kitten systemd[1]: Unit avahi-daemon.service entered
failed...e.
Oct 25 10:54:33 kitten avahi-daemon[474]: Failed to find group 'avahi'.
Oct 25 10:54:33 kitten systemd[1]: avahi-daemon.service: main process
exite...55
Oct 25 10:54:33 kitten systemd[1]: Unit avahi-daemon.service entered
failed...e.
Oct 25 10:54:33 kitten avahi-daemon[476]: Failed to find group 'avahi'.
Oct 25 10:54:33 kitten systemd[1]: avahi-daemon.service: main process
exite...55
Oct 25 10:54:33 kitten systemd[1]: Unit avahi-daemon.service entered
failed...e.
Oct 25 10:54:34 kitten avahi-daemon[478]: Failed to find group 'avahi'.
Oct 25 10:54:34 kitten systemd[1]: avahi-daemon.service: main process
exite...55
Oct 25 10:54:34 kitten systemd[1]: Unit avahi-daemon.service entered
failed...e.
Oct 25 10:54:34 kitten avahi-daemon[480]: Failed to find group 'avahi'.
Oct 25 10:54:34 kitten systemd[1]: avahi-daemon.service: main process
exite...55
Oct 25 10:54:34 kitten systemd[1]: Unit avahi-daemon.service entered
failed...e.
The last line repeats continually, with a ton of output, hundreds of lines per
second.
$ journalctl -b | grep avahi | wc -l
52539
I'm not sure it's related (perhaps the journal reserves space before filling it
in) but I upgraded my system to systemd only yesterday and my /var/log/journal
is already 520mb:
$ du -sh /var/log/journal/
520M /var/log/journal/</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>