devel

rsyslog 8.1.1 (v8-devel) released

This is the first bugfixing release for v8. It enhances overall stability and also re-enables some output modules. It is
highly suggested that v8 users upgrade to this release. Please note that it is still experimental code.

 

ChangeLog:

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

Download:

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

Feedback is *very much* appreciated.

Best regards,
Florian Riedl

Changelog for 8.1.1 (v8-devel)

Version 8.1.1 [devel] 2013-11-19

  • bugfix: STOP/discard(~) was mostly NOT honored
    This lead to execution of config code that was not meant to be executed.
  • bugfix: memory leak on worker thread termination
  • bugfix: potential segfault in omfile under heavy load
    Thanks to Pavel Levshin for alerting us.
  • bugfix: mmsequence: instance mode did not work
    Thanks to Pavel Levshin for the patch
  • bugfix: segfault on startup when certain script constructs are used
    e.g. “if not $msg …”
  • omhiredis: now supports v8 output module interface and works again
    Thanks to Pavel Levshin for the patch
  • mmaudit: now supports v8 output module interface and work again
  • bugfix: potential abort on startup in debug mode
    This depends on template type being used. The root cause was a non-necessary debug output, which were at the wrong spot (leftover from  initial testing).
    Thanks to Pavel Levshin for alerting us and providing a patch proposal.

rsyslog 8.1.0 (v8-devel) released

This is the initial and EXPERIMENTAL release of rsyslog v8. This release contains a rewritten core engine and is expected to perform much better in high performance environments with complex configurations (namely log normalization, Elasticsearch, Databases and remote forwarding).

We release this version in the hopes that interested parties have a look at it and provide feedback (including bug reports). However, it is NOT suitable for production use — for the time being please use rsyslog v7.5 for this.

More details can be found at:

http://blog.gerhards.net/2013/11/on-to-lucky-number.html

Please be also sure to review the compatibility document:

http://www.rsyslog.com/doc/v8compatibility.html

Feedback is *very much* appreciated.

 

ChangeLog:

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

Download:

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

 

Best regards,
Florian Riedl

Changelog for 8.1.0 (v8-devel)

Version 8.1.0 [devel] 2013-11-15

  • rewritten core engine for higher performance and new features In detail:
    • completely rewritten rule execution engine
    • completely changed output module interface
    • remodelled output module interface
    • enabled important output modules to support full concurrent operation

    The core engine has been considerably changed and must be considered experimental at this stage. Note that it does not yet include all features planned for v8, but is close to this goal. In theory, the engine should perform much better, especially on complex configurations and busy servers. Most importantly, actions instances can now be called concurrently from worker threads and many important output modules support multiple concurrent action instances natively.

  • module omruleset is no longer enabled by default.
    Note that it has been deprecated in v7 and been replaced by the “call” statement. Also, it can still be build without problems, the option must just explicitely be given.

 

Changelog for 7.5.6 (v7-devel)

Version 7.5.6 [devel] 2013-10-29

  • improved performance of RainerScript variable access
    by refactoring the whole body of variable handling code. This also
    solves some of the anomalies experienced in some versions of rsyslog.
    All variable types are now handled in unified code, including
    access via templates.
  • RainerScript: make use of 64 bit for numbers where available
    Thanks to Pavel Levshin for enhancement.
  • slight performance optimization if GCC is used
    We give branch prediction hints for the frequent RETiRet macro which is
    used for error handling. Some slight performance gain is to be expected
    from that.
  • removed global variable support
    The original idea was not well thought out and global variables, as
    implemented, worked far different from what anybody would expect. As
    such, we consider the current approach as an experiment that did not
    work out and opt to removing it, clearing the way for a better future
    solution. Note: global vars were introduced in 7.5.3 on Sept, 11th 2013.
  • new module mmsequence, primarily used for action load balancing
    Thanks to Pavel Levshin for contributing this module.
  • bugfix: unset statement always worked on message var, even if local
    var was given
  • bugfix: segfault if variable was assigned to non-container subtree
    Thanks to Pavel Levshin for the fix
  • bugfix: imuxsock did not suport addtl sockets if syssock was disabled
    Thanks to Pavel Levshin for the fix
  • bugfix: running imupd on multiple threads lead to segfault if recvmmsg
    is available
  • bugfix: segfault if re_extract() function was used and no match found
  • bugfix: omelasticsearch did not compile on platforms without atomic
    instructions
  • bugfix: potential misadressing on startup if property-filter was used
    This could happen if the property name was longer than 127 chars, a case
    that would not happen in practice.
  • bugfix: invalid property filter was not properly disabled in ruleset
    Note: the cosmetic memory leak introduced with that patch in 7.4.5 is
    now also fixed.

rsyslog 7.5.6 (v7-devel) released

This version contains new features and bug fixes. Most importantly, it contains a new module “mmsequence” (contributed by Pavel Levshin) which permits action load balancing. Also, variable access has been totally refactored and its processing speed improved. Note that this refactoring has some additional bug potential, so watch your system closely after the upgrade. Support for global variables has been removed, as the idea did not work out properly with the current core engine version and resulted in very unintuitive results (most folks would them simply call “wrong”…).
More detailed information is available in the changelog.

ChangeLog: http://www.rsyslog.com/changelog-for-7-5-6-v7-devel/

Download: http://www.rsyslog.com/rsyslog-7-5-6-v7-devel/

As always, feedback is appreciated.

Best regards,

Tim Eifler

Scroll to top