rsyslog 7.4.1 (v7-stable) released

This is a maintenance release, consisting primarily of bug fixes. Note that imjournal was extended to support rate-limiting, as this is needed as a safeguard for problems in systemd journal which in turn caused grief to rsyslog. See Rainer’s blog posting for more details:






As always, feedback is appreciated.

Best regards,
Florian Riedl

Changelog for 7.4.1 (v7-stable)

Version 7.4.1  [v7.4-stable] 2013-06-17

  • imjournal: add ratelimiting capability
    The original imjournal code did not support ratelimiting at all. We now have our own ratelimiter. This can mitigate against journal database corruption, when the journal re-sends old data. This is a current bug in systemd journal, but we won’t outrule this to happen in the future again. So it is better to have a safeguard in place. By default, we permit 20,000 messages witin 10 minutes. This may be a bit restrictive, but given the risk potential it seems reasonable.
    Users requiring larger traffic flows can always adjust the value.
  • bugfix: potential loop in rate limiting
    if the message that tells about rate-limiting gets rate-limited itself, it will potentially create and endless loop
  • bugfix: potential segfault in imjournal if journal DB is corrupted
  • bugfix: prevent a segfault in imjournal if state file is not defined
  • bugfix imzmq3: potential segfault on startup
    if no problem happend at startup, everything went fine
    Thanks to Hongfei Cheng and Brian Knox for the patch
Scroll to top