Changelog for 7.1.11 (v7-beta)
Version 7.1.11 [beta] 2012-10-16
- bugfix: imuxsock truncated head of received message
This happened only under some circumstances. Thanks to Marius Tomaschwesky, Florian Piekert and Milan Bartos for their help in solving this issue. - bugfix: do not crash if set statement is used with date field
Thanks to Miloslav Trmač for the patch. - change lumberjack cookie to “@cee:” from “@cee: ”
CEE originally specified the cookie with SP, whereas other lumberjack tools used it without space. In order to keep interop with lumberjack, we now use the cookie without space as well. I hope this can be changed in CEE as well when it is released at a later time.
Thanks to Miloslav Trmač for pointing this out and a similiar v7 patch. - added deprecated note to omruleset (plus clue to use “call”)
- added deprecated note to discard action (plus clue to use “stop”)
Changelog for 7.1.10 (v7-beta)
Version 7.1.10 [beta] 2012-10-11
- bugfix: m4 directory was not present in release tarball
- bugfix: small memory leak with string-type templates
- bugfix: small memory leak when template was specified in omfile
- bugfix: some config processing warning messages were treated as errors
- bugfix: small memory leak when processing action() statements
- bugfix: unknown action() parameters were not reported
Changelog for 6.5.1 (v6-beta)
Version 6.5.1 [BETA] 2012-10-11
- added tool “logctl” to handle lumberjack logs in MongoDB
- imfile ported to new v6 config interface
- imfile now supports config parameter for maximum number of submits
which is a fine-tuning parameter in regard to input baching - added pure JSON output plugin parameter passing mode
- ommongodb now supports templates
- bugfix: imtcp could abort on exit due to invalid free()
- bugfix: remove invalid socket option call from imuxsock
Thanks to Cristian Ionescu-Idbohrn and Jonny Törnbom - bugfix: missing support for escape sequences in RainerScript
only \’ was supported. Now the usual set is supported. Note that v5
used \x as escape where x was any character (e.g. “\n” meant “n” and NOT
LF). This also means there is some incompatibility to v5 for well-know
sequences. Better break it now than later. - bugfix: small memory leaks in template() statements
these were one-time memory leaks during startup, so they did NOT grow
during runtime - bugfix: config validation run did not always return correct return state
- bugfix: config errors did not always cause statement to fail
This could lead to startup with invalid parameters.
Changelog for 7.3.0 (v7-devel)
Version 7.3.0 [devel] 2012-10-09
- omlibdbi improvements, added
- support for config load phases & module() parameters
- support for default templates
- driverdirectory is now cleanly a global parameter, but can no longer be specified as an action paramter. Note that in previous versions this parameter was ignored in all but the first action definition
- improved omfile zip writer to increase compression This was achieved by somewhat reducing the robustness of the zip archive. This is controlled by the new action parameter “VeryReliableZip”.
Changelog for 7.1.8 (v7-beta)
Version 7.1.8 [beta] 2012-10-02
- bugfix: ruleset(){} directive errornously changed default ruleset much like the $ruleset legacy conf statement. This potentially lead to statements being assigned to the wrong ruleset.
- improved module doc
- added “parser” parameter to ruleset(), so that parser chain can be configured
- implemented “continue” RainerScript statement
Changelog for 7.1.6 (v7-devel)
Version 7.1.6 [devel] 2012-09-28
- implemented RainerScript input() statement, including support for it in major input plugins
- implemented RainerScript ruleset() statement
Changelog for 7.1.5 (v7-devel)
Version 7.1.5 [devel] 2012-09-26
- implemented RainerScript prifield() function
- implemented RainerScript field() function
- added new module imkmsg to process structured kernel log
Thanks to Milan Bartos for contributing this module - implemented basic RainerScript optimizer, which will speed up script
operations - bugfix: invalid free if function re_match() was incorrectly used
if the config file parser detected that param 2 was not constant, some
data fields were not initialized. The destructor did not care about that.
This bug happened only if rsyslog startup was unclean.
Changelog for 6.4.2 (v6-stable)
Version 6.4.2 [V6-STABLE] 2012-09-20
- bugfix: potential abort, if action queue could not be properly started
This most importantly could happen due to configuration errors. - bugfix: remove invalid socket option call from imuxsock
Thanks to Cristian Ionescu-Idbohrn and Jonny Törnbom - bugfix: missing support for escape sequences in RainerScript
only \’ was supported. Now the usual set is supported. Note that v5 used \x as escape where x was any character (e.g. “\n” meant “n” and NOT LF). This also means there is some incompatibility to v5 for well-known sequences. Better break it now than later. - bugfix: config validation run did not always return correct return state
Changelog for 7.1.4 (v7-devel)
Version 7.1.4 [devel] 2012-09-19
- implemented ability for CEE-based properties to be stored in disk queues
- implemented string concatenation in expressions via &-operator
- implemented json subtree copy in variable assignment
- implemented full JSON support for variable manipulation
- introduced “subtree”-type templates
- bugfix: omfile action did not respect “template” parameter
… and used default template in all cases - bugfix: MsgDup() did not copy CEE structure
This function was called at various places, most importantly during “last messages repeated n times” processing and omruleset. If CEE(JSON) data was present, it was lost as part of the copy process. - bugfix: debug output indicated improper queue type
Changelog for 7.1.3 (v7-devel)
Version 7.1.3 [devel] 2012-09-17
- introduced “set” and “unset” config statements
- bugfix: missing support for escape sequences in RainerScript only \’ was supported. Now the usual set is supported. Note that v5 used \x as escape where x was any character (e.g. “\n” meant “n” and NOT LF). This also means there is some incompatibility to v5 for well-know sequences. Better break it now than later.
- bugfix: invalid property name in property-filter could cause abort if action chaining (& operator) was used
http://bugzilla.adiscon.com/show_bug.cgi?id=355
Thanks to pilou@gmx.com for the bug report