devel

rsyslog 8.3.1 (v8-devel) released

We have just released 8.3.1 of the v8-devel branch.

This release provides some improvements for external message modification modules, a module to rewrite message facility and severity as well as bug fixes. It is a recommended update for all v8.3 users.

ChangeLog:

http://www.rsyslog.com/changelog-for-8-3-1-v8-devel/

Download:

http://www.rsyslog.com/download-v8-devel/

As always, feedback is appreciated.

Best regards,
Florian Riedl

Changelog for 8.3.1 (v8-devel)

Version 8.3.1 [v8-devel] 2014-04-24

  • external message modification interface now support modifying message PRI
  • “jsonmesg” property will include uuid only if one was previously generated
    This is primarily a performance optimization. Whenever the message uuid is gotten, it is generated when not already present. As we used the regular setter, this means that always the uuid was generated, which is quite time-consuming. This has now been changed so that it only is generated if it already exists. That also matches more closly the semantics, as “jsonmesg” should not make modifications to the message.
    Note that the same applies to “fulljson” passing mode for external plugins.
  • added plugin to rewrite message facility and/or severity
    Name: fac-sever-rewrite.py
  • permits to build against json-c 0.12
    Unfortunately, json-c had an ABI breakage, so this is necessary. Note that versions prior to 0.12 had security issues (CVE-2013-6370, CVE-2013-6371) and so it is desirable to link against the new version.
    Thanks to Thomas D. for the patch.
    Note that at least some distros have fixed the security issue in older versions of json-c, so this seems to apply mostly when building from sources.
  • bugfix: using UUID property could cause segfault
  • bugfix/mmexternal: memory leak
  • bugfix: memory leak when using “jsonmesg” property
  • bugfix: mmutf8fix did not detect two invalid sequences
    Thanks to Axel Rau for the patch.
  • bugfix: build problems with lexer.l on some platforms
    For some reason, the strdup() prototype and others are missing. I admit that I don’t know why, as this happens only in 8.3.0+ and there is no indication of changes to the affected files. In any case, we need to fix this, and the current solution works at least as an interim one.

rsyslog 8.3.0 (v8-devel) released

We have just released 8.3.0 of the v8-devel branch.

This opens the next iteration of the v8-devel branch. As its most important feature, this release offers the external plugin message modification interface and comes with a full sample of a credit card anonymizer in python.

ChangeLog:

http://www.rsyslog.com/changelog-for-8-3-0-v8-devel/

Download:

http://www.rsyslog.com/download-v8-devel/

Feedback is *very much* appreciated.

Best regards,
Florian Riedl

Changelog for 8.3.0 (v8-devel)

Version 8.3.0 [v8-devel] 2014-04-10

  • new plugin for anonymizing credit card numbers
    Thanks to Peter Slavov for providing the code.
  • external message modification modules are now supported
    They are bound via the new native module “mmexternal”. Also, a sample skeleton for an external python message modification module has been added.
  • new $jsonmesg property with JSON representation of whole message object
    closes: https://github.com/rsyslog/rsyslog/issues/19
  • improved error message for invalid field extraction in string template
    see also:
    http://kb.monitorware.com/problem-with-field-based-extraction-t12299.html
  • fix build problems on Solaris
  • NOTE: a json-c API that we begun to use requires the compiler to be in c99 mode. By default, we select it automatically. If you modify this and use gcc, be sure to include “-std=c99” in your compiler flags. This seems to be necessary only for older versions of gcc.

Changelog for 8.1.6 (v8-devel)

Version 8.1.6 [devel] 2014-02-20

  • omfile: permit to set global defaults for action parameters
    Thanks to Nathan Brown for the patch.
    See also: https://github.com/rsyslog/rsyslog/pull/23
  • add capability to escape control characters in the C way of doing it
    adds new global parameter “parser.escapeControlCharactersCStyle”
    Thanks to Nathan Brown for the patch.
    See also: https://github.com/rsyslog/rsyslog/pull/13
  • parser global parameters can now be set using RainerScript global()
    Thanks to Nathan Brown for the patch.
    See also: https://github.com/rsyslog/rsyslog/pull/23
  • omprog: guard program-to-be-executed against CTL-C
    This can frequently happen in debug mode, where rsyslog is terminated
    by ctl-c. In any case, SIGINT is not meant to control the child process,
    so it should be blocked.
  • omprog bugfix: parameter “forceSingleInstance” is NOT mandatory
  • add new jsonr property replacer option
    Thanks to Nathan Brown for the patch.
  • added external plugin interface
  • ommongodb: add authentication support (untested)
    Thanks to JT for the patch.
    See also: https://github.com/rsyslog/rsyslog/pull/17
  • bugfix: json templates are improperly created
    Strings miss the terminating NUL character, which obviously can lead
    to all sorts of problems.
    See also: https://github.com/rsyslog/rsyslog/issues/27
    Thanks to Alain for the analysis and the patch.
  • ompgsql bugfix: improper handling of auto-backgrounding mode
    If rsyslog was set to auto-background itself (default code behaviour, but
    many distros now turn it off for good reason), ompgsql could not
    properly connect. This could even lead to a segfault. The core reason
    was that a PG session handle was kept open over a fork, something that
    is explicitely forbidden in the PG API.
    Thanks to Alain for the analysis and the patch.
  • bugfix: ommongodb’s template parameter was mandatory but should have
    been optional
    Thanks to Alain for the analysis and the patch.
  • bugfix: end of batch processing was not 100% correct. Could lead to
    outputs not properly wirting messages. At least omelasticsearch did not
    write anything to the database due to this bug.
    See: https://github.com/rsyslog/rsyslog/issues/10
    Thanks to Radu Gheorghe for reporting the issue.

rsyslog 8.1.5 (v8-devel) released

We have just released 8.1.5 of the v8-devel branch. This release offers some important bug fixes and an enhanced imfile. It now supports inotify and has no longer a fixed limit on the number of files that can be monitored. Note that inotify must be enabled. By default, the previous polling mode is used. For details see parameter “mode” in the doc: http://www.rsyslog.com/doc/imfile.html
ChangeLog: http://www.rsyslog.com/changelog-for-8-1-5-v8-devel/
Download: http://www.rsyslog.com/rsyslog-8-1-5-v8-devel/

Feedback is *very much* appreciated.

Best regards, Florian Riedl

Changelog for 8.1.5 (v8-devel)

Version 8.1.5 [devel] 2014-01-24

  • imfile now supports inotify (but must be explicitely turned on)
  • imfile no longer has a limit on number of monitored files
  • added ProcessInternalMessages global system parameter
    This permits to inject rsyslog status messages into *another* main syslogd or the journal.
  • new dependency: liblogging-stdlog (for submitting to external logger)
  • bugfix: imuxsock input parameters were not accepted due to copy&paste error. Thanks to Andy Goldstein for the fix.

rsyslog 8.1.4 (v8-devel) released

We have just released 8.1.4 of the v8-devel branch.

This release adds the capability to set a variable based on a template. It also adds KEEPALIVE support to the RELP modules (which now require librelp 1.2.2+ for this reason). It also adds some usability enhancements and bug fixes.

Note that this release can be considered a “normal” devel version, with moderate risk associated to it. Experience in the past weeks suggest so. Special thanks to Pavel Levshin for all his work and tests. Still note that there is a considerably higher risk running the devel version than the stable one.

ChangeLog:

http://www.rsyslog.com/changelog-for-8-1-4-v8-devel/

Download:

http://www.rsyslog.com/rsyslog-8-1-4-v8-devel/

Feedback is *very much* appreciated.

Best regards,
Florian Riedl

Scroll to top