Changelog for 7.2.2 (v7-stable)

Version 7.2.2 [v7-stable] 2012-10-16

  • doc improvements
  • enabled to build without libuuid, at loss of uuid functionality
    this enables smoother builds on older systems that do not support
    libuuid. Loss of functionality should usually not matter too much as
    uuid support has only recently been added and is very seldom used.
  • bugfix: omfwd did not properly support “template” parameter
  • bugfix: potential segfault when re_match() function was used
    Thanks to oxpa for the patch.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=371
  • bugfix: potential abort of imtcp on rsyslogd shutdown
  • bugfix: imzmq3 segfault with PULL subscription
    Thanks to Martin Nilsson for the patch.
  • bugfix: improper handling of backslash in string-type template()s
  • bugfix: leading quote (“) in string-type template() lead to thight loop
    on startup
  • bugfix: no error msg on invalid field option in legacy/string template
  • bugfix: potential segfault due to invalid param handling in comparisons
    This could happen in RainerScript comparisons (like contains); in some
    cases an unitialized variable was accessed, which could lead to an
    invalid free and in turn to a segfault.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=372
    Thanks to Georgi Georgiev for reporting this bug and his great help
    in solving it.
  • bugfix: no error msg on unreadable $IncludeConfig path
  • bugfix: $IncludeConfig did not correctly process directories
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=376
    The testbench was also enhanced to check for these cases.
    Thanks to Georgi Georgiev for the bug report.
  • bugfix: make rsyslog compile on kfreebsd again
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=380
    Thanks to Guillem Jover for the patch
  • bugfix: garbled message if field name was used with jsonf property option
    The length for the field name was invalidly computed, resulting in either
    truncated field names or including extra random data. If the random data
    contained NULs, the rest of the message became unreadable.
  • bugfix: potential segfault at startup with property-based filter
    If the property name was followed by a space before the comma, rsyslogd
    aborted on startup. Note that no segfault could happen if the initial
    startup went well (this was a problem with the config parser).
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=381
  • bugfix: imfile discarded some file parts
    File lines that were incomplete (LF missing) *at the time imfile polled
    the file* were partially discarded. That part of the line that was read
    without the LF was discarded, and the rest of the line was submitted in
    the next polling cycle. This is now changed so that the partial content
    is saved until the complete line is read. Note that the patch affects
    only read mode 0.
    Thanks to Milan Bartos for providing the base idea for the solution.

rsyslog 7.3.3 (v7-devel) released

We have just released 7.3.3 of the v7-devel branch. This release most importantly provides increased performance for the disk queue subsystem. Especially CPU-use will be much lower when unspooling disk queues. It also contains all known fixes for v7, some imported from v7-stable and earlier versions.

 

ChangeLog:

http://www.rsyslog.com/changelog-for-7-3-3-v7-devel/

Download:

http://www.rsyslog.com/rsyslog-7-3-3-v7-devel/

As always, feedback is appreciated.

Best regards,

Florian Riedl

Changelog for 7.3.3 (v7-devel)

Version 7.3.3  [devel] 2012-11-07

  • improved disk queue performance
  • bugfix: dynafile zip files could be corrupted
    This could happen if a dynafile was destructed before the first write. In practice, this could happen if few lines were written to a file and it then became evicted from the dynafile cache. This would probably look very random, because it depended on the timing in regard to message volume and dynafile cache size.

rulesets and rsyslog 7.2+

In rsyslog 7.2.0 we introduced some interesting config enhancements. Among these are changes to how rulesets can be specified or called. A ruleset is basically looking like this:

ruleset(name="rulesetname") { statements here }

As you can see, you specify a ruleset by its name. All statements that will be specified go into the curly brackets. In addition, a ruleset can be called by another ruleset. This is simply done by call rulesetname The rulesetname is just plainly specified. We hope this to be more intuitively. Here is a larger example (bascially taken from the rsyslog mailing list, thanks to Brian Knox). module(load="imptcp" keepalive="on") # use imptcp just as example for bind ruleset below ruleset(name="rs1") { *.* /var/log/test1.log } ruleset(name="rs2") { *.* /var/log/test2.log call rs1 } input(type="imptcp" port="13514" ruleset="rs2") All statements, which are NOT specified in a ruleset will be automatically inserted into the default ruleset.

Legacy $Ruleset statements are still supported, but cannot be cross-used with the new ruleset() statements.

rsyslog 7.3.2 (v7-devel) released

This release introduced a totally new rate-limiting system for all modules as well as much better “last message repeated n times” handling. For details, please see Rainer’s blog at

http://blog.gerhards.net/2012/10/rate-limiting-in-rsyslog-732.html

Besides this feature, the version also includes enhancements for omelasticsearch as well as input batching support for imudp (which should provide some performance boost on very busy systems). Also, action-like statements (call, stop, …) are now supported in action lists. Of course, there are also some bugfixes, many imported from v6 and v7.2.

ChangeLog:

http://www.rsyslog.com/changelog-for-7-3-2-v7-devel/

Download:

http://www.rsyslog.com/rsyslog-7-3-2-v7-devel/

As always, feedback is appreciated.

Best regards,
Tim Eifler

Changelog for 7.3.2 (v7-devel)

Version 7.3.2 [devel] 2012-10-30

  • totally reworked ratelimiting and “last message repeated n times”
    all over rsyslog code. Each of the supported inputs now supports
    linux-like ratelimiting (formerly only imuxsock did). Also, the
    “last message repeated n times” is now processed at the input side
    and no longer at the output side of rsyslog processing. This
    provides the basis for new future additions as well as usually more
    performance and a much simpler output part (which can be even further
    refactored).
  • imtcp: support for Linux-Type ratelimiting added
  • imptcp: support for Linux-Type ratelimiting added
  • imudp enhancements:
    • support for input batching added (performance improvement)
    • support for Linux-Type ratelimiting added
  • permited action-like statements (stop, call, …) in action lists
  • bugfix: segfault on startup when modules using MSG_PASSING mode are used
  • omelasticsearch: support for writing data errors to local file added
  • omelasticsearch: fix check for bulk processing status response
Scroll to top