<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 floods its own logs and eats the all the CPU"
href="https://bugs.freedesktop.org/show_bug.cgi?id=62958">62958</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>systemd floods its own logs and eats the all the CPU
</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>higuita@gmx.net
</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>Reporting problem upstream, as requested in
<a href="https://bugs.archlinux.org/task/33990">https://bugs.archlinux.org/task/33990</a>
here is a copy of the problem reported:
+++++++++++++++++++++++++++++++
I made a mistake configuring the syslog-ng (my fault) and a few minutes later
found that systemd was eating all the cpu.
A simple dmesg showed the problem:
[ 865.485322] systemd[1]: syslog-ng.service start request repeated too quickly,
refusing to start.
trying to find the origin of the problem, i got:
# journalctl -xn
-- Logs begin at Sáb 2013-02-23 21:22:54 WET, end at Dom 2013-02-24 01:37:39
WET. --
Fev 24 01:37:39 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
Fev 24 01:37:39 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
Fev 24 01:37:39 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
Fev 24 01:37:39 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
Fev 24 01:37:39 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
Fev 24 01:37:39 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
Fev 24 01:37:39 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
Fev 24 01:37:39 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
Fev 24 01:37:39 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
Fev 24 01:37:39 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
# systemctl status syslog-ng.service
syslog-ng.service - System Logger Daemon
Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled)
Active: failed (Result: start-limit) since Dom 2013-02-24 01:37:58 WET; 5s ago
Docs: man:syslog-ng(8)
Process: 2494 ExecStart=/usr/sbin/syslog-ng -F (code=exited, status=1/FAILURE)
Fev 24 01:38:02 paquete.motaleite.net systemd[1]: Failed to start System Logger
Daemon.
Fev 24 01:38:02 paquete.motaleite.net systemd[1]: Failed to start System Logger
Daemon.
Fev 24 01:38:02 paquete.motaleite.net systemd[1]: Failed to start System Logger
Daemon.
Fev 24 01:38:02 paquete.motaleite.net systemd[1]: Failed to start System Logger
Daemon.
Fev 24 01:38:02 paquete.motaleite.net systemd[1]: Failed to start System Logger
Daemon.
Fev 24 01:38:02 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
Fev 24 01:38:02 paquete.motaleite.net systemd[1]: Failed to start System Logger
Daemon.
Fev 24 01:38:02 paquete.motaleite.net systemd[1]: Failed to start System Logger
Daemon.
Fev 24 01:38:02 paquete.motaleite.net systemd[1]: Failed to start System Logger
Daemon.
Fev 24 01:38:02 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
Fev 24 01:38:02 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
Fev 24 01:38:02 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
Fev 24 01:38:02 paquete.motaleite.net systemd[1]: syslog-ng.service start
request repeated too quickly, refusing to start.
so only useless info because systemd is busy flooding its own logs, hiding the
real problem.
after some tries using systemd, i gave up and debug syslog-ng manually:
# /usr/sbin/syslog-ng -F
Error parsing config, duplicate destination definition in
/etc/syslog-ng/syslog-ng.conf at line 96, column 1:
destination d_mail { file("/var/log/maillog"); };
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
syslog-ng documentation:
<a href="http://www.balabit.com/support/documentation/?product=syslog-ng">http://www.balabit.com/support/documentation/?product=syslog-ng</a>
mailing list: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a>
So there, this is what systemd should have reported in the very beginning!
So what i recommend is that systemd should merge identical messages or at very
least, ignore it own flood messages
++++++++++++++++++++++
Of course, even without the log flooding, the respawn of a failling daemon too
fast is also a problem, it only eats cpu and logs... i can also open one bug
for this one if you want.</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>