<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 --- - Journal: High-volume repeating pair of messages not suppressed"
href="https://bugs.freedesktop.org/show_bug.cgi?id=68000">68000</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>Journal: High-volume repeating pair of messages not suppressed
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>critical
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>awilliam@redhat.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</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>I just looked at the journalctl output on my laptop, and saw this:
Aug 10 18:41:52 laptop.localdomain systemd[1]: systemd-journald.service: main
process exited, code=killed, status=10/USR1
Aug 10 18:41:52 laptop.localdomain systemd[1]: Started Trigger Flushing of
Journal to Persistent Storage.
Aug 10 18:41:52 laptop.localdomain systemd-journal[28662]: Allowing system
journal files to grow to 4.0G.
Aug 10 18:41:52 laptop.localdomain systemd-journal[28662]: Journal started
Aug 10 18:41:52 laptop.localdomain systemd[1]: systemd-journald.service: main
process exited, code=exited, status=1/FAILURE
Aug 10 18:41:52 laptop.localdomain systemd-journal[28665]: Allowing system
journal files to grow to 4.0G.
Aug 10 18:41:52 laptop.localdomain systemd-journal[28665]: Journal started
Aug 10 18:41:52 laptop.localdomain systemd[1]: Started Trigger Flushing of
Journal to Persistent Storage.
Aug 10 18:41:52 laptop.localdomain systemd[1]: systemd-journald.service: main
process exited, code=exited, status=1/FAILURE
Aug 10 18:41:52 laptop.localdomain systemd[1]: Started Trigger Flushing of
Journal to Persistent Storage.
Note it's now 14:19 on August 11, so it appears that journald has pretty much
given up and gone home...
Looking in /var/log/journal, clearly something has spammed the journal in a
major way:
[adamw@laptop fbb0c4896a9c0f680475c0a07edd2c5a]$ pwd
/var/log/journal/fbb0c4896a9c0f680475c0a07edd2c5a
[adamw@laptop fbb0c4896a9c0f680475c0a07edd2c5a]$ du -h
2.7G .
Eyeballing the journalctl output, what I'm seeing is a whole huge bunch of
this:
Jun 27 02:53:35 laptop.localdomain kernel: psmouse serio1: Trackpad at
isa0060/serio1/input0 - driver resynced.
Jun 27 02:53:35 laptop.localdomain kernel: psmouse serio1: Trackpad at
isa0060/serio1/input0 lost sync at byte 1
Jun 27 02:53:35 laptop.localdomain kernel: psmouse serio1: Trackpad at
isa0060/serio1/input0 - driver resynced.
Jun 27 02:53:35 laptop.localdomain kernel: psmouse serio1: Trackpad at
isa0060/serio1/input0 lost sync at byte 1
over and over and over and over again - there are literally hundreds of those
messages each second at some points.
It seems like the rate limiting stuff is not catching this case for some
reason; maybe it doesn't handle repeating pairs of messages like this?</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>