Red Hat Bugzilla – Bug 1030523
when journald discards messages due to rate limiting, it does not show how many messages were dropped
Last modified: 2015-02-17 14:59:33 EST
Created attachment 824014 [details]
/etc/rc.d/init.d/verbose to show behavior of journald rate-limiting
Description of problem:
As documented in 'man journald.conf', systemd-journald applies rate limiting based on RateLimitInterval and RateLimitBurst to messages on a per-service basis. The default value for RateLimitBurst is 200. One of my services is very verbose and produces over 200 messages when it starts. As expected, journald starts discarding messages after 200 are logged. But the man page claims that it will log a message about the number of dropped messages, and I do not see that in the log. It would be very helpful if journald shows that it dropped messages.
Version-Release number of selected component (if applicable):
Create a service or LSB init script that logs over 200 messages in less than 10 seconds. Start the service and observe that messages are dropped. The attached LSB init script demonstrates the problem. Note that there is another bug I discovered: if the script spews 250 messages quickly without pausing, none are discarded by journald. If I add "sleep 1" after every 50 messages, then the rate limiting works propertly. Maybe I should open a separate bug for this issue...
Steps to Reproduce:
1. Copy the attached file to /etc/rc.d/init.d/verbose
2. In one window, run "journalctl -f"
3. systemctl start verbose
Messages are discarded without any message indicating that messages were dropped.
Journald should log a message saying how many messages were dropped.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
This was fixed at some point.