rsyslog

The rocket-fast system for log processing

v8

rsyslog 8.1.3 (v8-devel) released

By Adiscon SupportPosted on Posted in News, Release AnnouncementTagged , , , , , ,

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

This release contains further performance improvements. Note that both the output module interface and strgen interface have been changed and (some) modules may need to be modified. For the v8 supported rsyslog provided modules this has already be done (see v8 compatibility document for a list of supported modules). This release also detects failed actions more precisely. Finally, there are a couple of bug fixes in this release.

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-3-v8-devel/

Download:

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

Feedback is *very much* appreciated.

Best regards,
Florian Riedl

Changelog for 8.1.3 (v8-devel)

By Adiscon SupportPosted on Posted in ChangelogTagged , , , , , , ,

Version 8.1.3 [devel] 2013-12-06

THIS VERSION CAN BE CONSIDERED A “NORMAL” DEVEL RELEASE. It’s no longer
highly experimental. This assertion is based on real-world feedback.

  • changes to the strgen module interface
  • new output module interface for transactional modules
  • performance improvements
    • reduced number of malloc/frees due to further changes to the output module interface
    • reduced number of malloc/frees during string template processing
      We now re-use once allocated string template memory for as long as the worker thread exists. This saves us from doing new memory allocs (and their free counterpart) when the next message is processed. The drawback is that the cache always is the size of the so-far largest message processed. This is not considered a problem, as in any case a single messages’ memory footprint should be far lower than that of a whole set of messages (especially on busy servers).
    • used variable qualifiers (const, __restrict__) to hopefully help the compiler generate somewhat faster code
  • failed action detection more precisely for a number of actions
    If an action  uses string parameter passing but is non-transactional it can be executed immediately, giving a quicker indicatio of action failure.
  • bugfix: limiting queue disk space did not work properly
    • queue.maxdiskspace actually initializes queue.maxfilesize
    • total size of queue files was not checked against queue.maxdiskspace for disk assisted queues.

    Thanks to Karol Jurak for the patch.

rsyslog 8.1.2 (v8-devel) released

By Adiscon SupportPosted on Posted in News, Release AnnouncementTagged , , , , , ,

We have just released 8.1.2 of the v8-devel branch. This is primarily a maintenance release, but offers some improvements. Thanks to Pavel Levshin, mmnormalize now offers higher performance and we have added the ability to link directly to jemalloc. Also, usability of queue settings has been improved by using better (and dynamic) defaults for a range of settings.

ChangeLog:

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

Download:

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

Feedback is *very much* appreciated.

Best regards,
Florian Riedl

Changelog for 8.1.2 (v8-devel)

By Adiscon SupportPosted on Posted in ChangelogTagged , , , , , , ,

Version 8.1.2 [devel] 2013-11-28

  • support for liblognorm1 added – results in performance improvements
    Thanks to Pavel Levshin for his work in this regard.
  • support for jemalloc added via –enable-jemalloc
    Thanks to Pavel Levshin for suggesting jemalloc
  • queue defaults have changed
    •   high water mark is now dynamically 90% of queue size
    •   low water makr is now dynamically 70% of queue size
    •   queue.discardMark is now dynamically 98% of queue size
    •   queue.workerThreadMinimumMessage set to queue.size / num workers

    For queues with very low queue.maxSize (< 100), “emergency” defaults will be used.
    Note that build system is experimental at this stage.

  • bugfix: disk queues created files in wrong working directory
    if the $WorkDirectory was changed multiple times, all queues only used the last value set.
  • bugfix: legacy directive $ActionQueueWorkerThreads was not honored
  • bugfix: mmrfc5424addhmac: “key” parameter was not properly processed

rsyslog 8.1.1 (v8-devel) released

By Adiscon SupportPosted on Posted in News, Release AnnouncementTagged , , , , ,

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)

By Adiscon SupportPosted on Posted in ChangelogTagged , , , , ,

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

By Adiscon SupportPosted on Posted in News, Release AnnouncementTagged , , , , ,

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

Scroll to top