Changelog

Changelog for 7.6.4 (v7-stable)

Version 7.6.4 [v7.6-stable] 2014-09-12

  • add –enable-generate-man-pages configure switch (default: enabled)
    This forces generation of man pages, even if cached ones exists. This “fixes” a typical release tarball nit. While it is hackish, the benefit is clear given the history of failed tarball releases since we changed the cached man page handling. It was just too easy to get that wrong.
  • removed obsolete –disable-fsstnd configure option
    Thanks to Thomas D. for alerting us.
    Closes: https://github.com/rsyslog/rsyslog/issues/72
  • 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.
  • new omfile default module parameters
    • filecreatemode
    • fileowner
    • fileownernum
    • filegroup
    • filegroupnum
    • dirowner
    • dirownernum
    • dirgroup
    • dirgroupnum

    Thanks to Karol Jurak for the patch.

  • bugfix: memory leak in TCP TLS mode
  • bugfix: imfile: if a state file for a different file name was set, that different file (name) was monitored instead of the configured one. Now, the state file is deleted and the correct file monitored.
    closes: https://github.com/rsyslog/rsyslog/issues/103
  • bugfix: using UUID property could cause segfault
  • bugfix: mmutf8fix did not detect two invalid sequences
    Thanks to Axel Rau for the patch.
  • bugfix: file descriptor leak with Guardtime signatures
    When a .gtstate file is opened it is never closed. This is especially bad when dynafiles frequently get evicted from dynafile cache and be re-opened again.
  • bugfix: busy loop in tcp listener when running out of file descriptors
    Thanks to Susant Sahani for the patch.
  • bugfix: mishandling of input modules not supporting new input instances
    If they did not support this, accidently the output module part of the module union was written, leading to unpredictable results. Note: all core modules do support this interface, but some contributed or very old ones do not.
  • bugfix: double-free when ruleset() parser parameters were used
    While unlikely, this could cause stability issues even after the config phase.
  • bugfix: output modules with parameters with multiple passing modes could caused strange behaviour including aborts
    This was due to the fact that the action module only preserved and processed the last set passing mode. Note that this was not a problem for the plugins provided by the rsyslog git: none of them uses different passing modes.
    Thanks to Tomas Heinrich for providing a very detailled bug report.
  • various fixes after coverty scan
    These do not address issues seen in practice but those seen by the tool. Some of them may affect practical deployments.
    Thanks to Tomas Heinrich for the patches.
  • bugfix imuxsock: “Last message repeated…” was not emitted at shutdown
    The “Last message repeated…” notice didn’t get printed if rsyslog was shut down before the repetition was broken.
    Thanks to Tomas Heinrich for the patch.
  • bugfix: make dist failed when GUARDTIME or LIBGCRYPT feature was disabled
  • bugfix: mmjsonparse did not build with json-c < 0.10
    This was a regression introduced some time in the past in order to support API changes in json-c. Now we check for the version and use proper code.
  • bugfix: mmanon did not properly anonymize IP addresses starting with ‘9’
    Thanks to defa-at-so36.net for reporting this problem.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=529

Changelog for 8.3.4 (v8-devel)

Version 8.3.4 [v8-devel] 2014-07-11

  • new pmciscoios parser supporting various Cisco IOS formats
  • RFC3164 timestamp parser now accepts timezones and subsecond resolution
    … at least for some common formats and where we could do so without running risk of breaking proper formats (or introducing regressions)
  • new parser config object — permits to define custom parser definitions
  • new tzinfo config object — permits to define time zone offsets
    This is a utility object that currently is being used by some parsers.
  • bugfix: mishandling of input modules not supporting new input instances
    If they did not support this, accidently the output module part of the module union was written, leading to unpredictable results. Note: all core modules do support this interface, but some contributed or very old ones do not.
  • bugfix: double-free when ruleset() parser parameters were used
    While unlikely, this could cause stability issues even after the config phase.

Changelog for 8.3.3 (v8-devel)

Version 8.3.3 [v8-devel] 2014-05-26
  • unify input object naming
    imudp now supports “name” paramter, as other inputs do. “inputname” has been deprecated, but can still be used. Same applies to “appendport” subparamter”. Thanks to “Nick Syslog” for the suggestion.
  • made the missing (contributed) modules build under v8 [import from 8.2.2]
    Modules:

    • * mmrfc5424addhmac
    •   * omrabbitmq
    •   * omgssapi
    •   * omhdfs
    •   * omzmq3
  • added a cleanup process (janitor); permits to close omfile files after a timeout
  • make omgssapi build under v8.3 [import vom v8.2]
    note that we could do this to the stable, because there is NO regression chance at all: only omgssapi was changed, and this module did NOT work previously.
  • removed obsolete –disable-fsstnd configure option
    Thanks to Thomas D. for alerting us.
    Closes: https://github.com/rsyslog/rsyslog/issues/72

Changelog for 8.2.2 (v8-stable)

Version 8.2.2 [v8-stable] 2014-06-02

  • made the missing (contributed) modules build under v8
    Note that we could do this to the stable, because there is NO regression chance at all: only the modules themselves were changed, and they did NOT work at all previously. Please also note that most of these modules did not yet receive real testing. As we don’t have the necessary environments (easily enough available), we depend on users submitting error reports and helping to iron out any issues that may arise.
    Modules:

    • mmrfc5424addhmac
    • omrabbitmq
    • omgssapi
    • omhdfs
    • omzmq3

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.

Changelog for 8.2.1 (v8-stable)

Version 8.2.1 [v8-stable] 2014-04-17

  • 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.
  • doc is no longer shipped as part of the rsyslog tarball
    Instead, the rsyslog-doc project creates its own tarball. This is the result of a mailing list discussion after the 8.2.0 release with a tarball-in-tarball approach, which was disliked by almost all distro maintainers. This move also has the advantage of de-coupling the release cycles of both projects a bit (which turned out to be a bit problematic in practice).
  • bugfix: mmutf8fix did not detect two invalid sequences
    Thanks to Axel Rau for the patch.

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.

rsyslog 8.2.0 (v8-stable) released

This is the first release of the greatly improved version 8 of rsyslog. Large parts of the core engine have been rewritten in order to support even greater performance and newly things like global variable support in RainerScript. The new engine is the foundation for the next couple of years of rsyslog technology. As another major design feature, an interface for external plugins has been added. Version 8.2 supports external output plugins, but external message modification and input plugins are also schedule to appear soon.
With the release of version 8, 7.6 is being as officially supported stable. However, we will support 7.6 for some while. So there is no urgent need to upgrade to v8.
ChangeLog:

http://www.rsyslog.com/changelog-for-8-2-0-v8-stable/

Download:

http://www.rsyslog.com/downloads/download-v8-stable/

As always, feedback is appreciated.

Best regards,
Florian Riedl

Changelog for 8.2.0 (v8-stable)

Version 8.2.0 [v8-stable] 2014-04-02
This starts a new stable branch based on 8.1.6 plus the following changes:

  • we now use doc from the rsyslog-doc project
    As such, the ./doc subtree has been removed. Instead, a cache of the rsyslog-doc project’s files has been included in ./rsyslog-doc.tar.gz. Note that the exact distribution mode for the doc is still under discussion and may change in future releases. This was agreed upon on the rsyslog mailing list. For doc issues and corrections, be sure to work with the rsyslog-doc project. It is currently hosted at https://github.com/rsyslog/rsyslog-doc
  • add support for specifying the liblogging-stdlog channel spec
    new global parameter “stdlog.channelspec”
  • add “defaultnetstreamdrivercertfile” global variable to set a default for the certfile.
    Thanks to Radu Gheorghe for the patch.
  • omelasticsearch: add new “usehttps” parameter for secured connections
    Thanks to Radu Gheorghe for the patch.
  • “action resumed” message now also specifies module type which makes troubleshooting a bit easier. Note that we cannot output all the config details (like destination etc) as this would require much more elaborate code changes, which we at least do not like to do in the stable version.
  • add capability to override GnuTLS path in build process
    Thanks to Clayton Shotwell for the patch
  • better and more consistent action naming, action queues now always contain the word “queue” after the action name
  • bugfix: ompipe did resume itself even when it was still in error
    See: https://github.com/rsyslog/rsyslog/issues/35
    Thanks to github user schplat for reporting
Scroll to top