rsyslog 8.1.6 (v8-devel) released

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

This is the release candidate for v8.2.0 stable. It contains a number if smaller enhancements as well as bug fixes. We plan to release 8.2.0 soon. So we would appreciate if you could report any bugs you find in that version.

ChangeLog:

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

Download:

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

Feedback is *very much* appreciated.

Best regards,
Tim Eifler

rsyslog 7.6.0 (v7-stable) released

This is the first release of rsyslog 7.6 in the v7-stable branch. Since 7.4 a lot of new functions have found their way into rsyslog. With 7.6 being the successor of the 7.5 development branch, everything that has been added there has now found its way into the stable version. The major additions consist of

  • imrelp/omrelp now support TLS & (zip) compression
  • impstats is now emitting resource usage counters, can directly emit delta values and can now be bound to a ruleset
  • mmpstrucdata is a new module to parse RFC5424 structured data into JSON message properties
  • mmutf8fix is a new module to fix invalid UTF-8 sequences
  • mmsequence is a new module that helps with action load balancing
  • new defaults for main/ruleset queues to be more enterprise-like

Also the new stable version has undergone a lot of bug fixes, performance improvements and optimizations that make rsyslog 7.6 a lot more reliable and performing than before. Also, requirements have changed a little. For rsyslog 7.6 you now require librelp 1.1.4 and libestr 0.1.7 due to major fixes.

More detailed information is available in the ChangeLog.

ChangeLog: http://www.rsyslog.com/changelog-for-7-6-0-v7-stable/

Download: http://www.rsyslog.com/rsyslog-7-6-0-v7-stable/

As always, feedback is appreciated.

Best regards,

Florian Riedl

Changelog for 7.6.0 (v7-stable)

Version 7.6.0 [v7.6-stable] 2014-01-??
This starts a new stable branch based on 7.5.8 plus the following changes:

  • bugfix: imuxsock input parameters were not accepted due to copy&paste error.
    Thanks to Andy Goldstein for the fix.
  • 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: 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.

Changelog for 7.4.10 (v7-stable)

Version 7.4.10 [v7.4-stable] 2014-02-12

  • 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.

LibLogging 1.0.1 released

liblogging 1.0.1 [download]

This version primarily clarifies the licensing and fixes some packaging issues. Otherwise, it is identical to 1.0.0.

Changelog:
v1.0.1 2014-02-10
– rfc3195 component now 2-clause BSD licensed
  This means the complete liblogging is now under 2-clause BSD
– new component names:
  * liblogging-stdlog
  * liblogging-rfc3195
  made some necessary name adjustments
  See also: https://github.com/rsyslog/liblogging/issues/2

sha256sum: 99d09101cc3c22e2388fe2a817bb1c6f5fe2275623aadb94a49d1c2259102bfa

Scroll to top