[systemd-bugs] [Bug 68000] New: Journal: High-volume repeating pair of messages not suppressed

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=68000

          Priority: medium
            Bug ID: 68000
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: Journal: High-volume repeating pair of messages not
                    suppressed
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: critical
    Classification: Unclassified
                OS: Linux (All)
          Reporter: awilliam at redhat.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

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 at laptop fbb0c4896a9c0f680475c0a07edd2c5a]$ pwd
/var/log/journal/fbb0c4896a9c0f680475c0a07edd2c5a
[adamw at 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?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130811/1ef9bac2/attachment.html>