rsyslog

High-performance log ingestion and ETL engine

rsyslog

High-performance log ingestion and ETL engine

Author : adisconteam

Changelog for 5.5.7 (v5-beta)

adisconteamChangelog, , ,

Version 5.5.7  [V5-BETA] (rgerhards), 2010-08-09

  • changed omudpspoof default spoof address to simplify typical use casethanks to David Lang for suggesting this
  • doc bugfix: pmlastmsg doc samples had errors
  • bugfix[minor]: pmrfc3164sd had invalid name (resided in rsyslog namespace, what should not be the case for a contributed module)
  • added omuxsock, which permits to write message to local Unix socketsthis is the counterpart to imuxsock, enabling fast local forwarding

Changelog for 3.2.2 (v3-stable)

adisconteamChangelog, , ,

Version 3.22.2 [v3-stable] (rgerhards), 2010-08-05

  • bugfix: comment char (‘#’) in literal terminated script parsing and thus could not be used.
    but tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=119
  • enhance: imrelp now also provides remote peer’s IP address[if librelp != 1.0.0 is used]
  • bugfix: sending syslog messages with zip compression did not work
  • bugfix: potential hang condition on queue shutdown
  • bugfix: segfault on startup when -q or -Q option was given
    bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=157
    Thanks to Jonas Nogueira for reporting this bug.
  • clarified use of $ActionsSendStreamDriver[AuthMode/PermittedPeers]in doc set (require TLS drivers)
  • bugfix: $CreateDirs variable not properly initialized, default thuswas random (but most often “on”)
  • bugfix: potential segfault when -p command line option was usedthanks to varmojfekoj for pointing me at this bug
  • bugfix: programname filter in ! configuration can not be resetThanks to Kiss Gabor for the patch.

rsyslog 5.5.6 (devel) released

adisconteamNews, Release Announcement, ,

Hi all,

We have just released rsyslog 5.5.6, a member of the devel branch.

The new release provides exciting performance enhancements: on multicore-machines it can be many times faster than version 5.5.5 (which already was quite fast). Most importantly, the enhancement provides much better scalability, so adding many additional core gains much more speedup than with any previous version.

A new concept of “strgen” modules has been implemented, which permit to use high speed C code as templates. Also, support for malformed “last message repated n times” messages, as emited by some syslogds, has been added in form of a custom message parser.

There are also a couple of bugfixes and minor improvements.

See ChangeLog for more details.

ChangeLog:

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

Download:

http://www.rsyslog.com/rsyslog-5-5-6-devel

As always, feedback is appreciated.

Best regards,
Tom Bergfeld

Changelog for 5.5.6 (devel)

adisconteamChangelog, ,

Version 5.5.6  [DEVEL] (rgerhards), 2010-07-21

  • added parser modules
    • pmlastmsg, which supports the notoriously malformed “last message repeated n times” messages from some syslogd’s (namely sysklogd)
    • pmrfc3164sd (contributed), supports RFC5424 structured data in RFC3164 messages [untested]
  • added new module type “string generator”, used to speed up output processing. Expected speedup for (typical) rsyslog processing is roughly 5 to 6 percent compared to using string-based templates.
    They may also be used to do more complex formatting with custom C code, what provided greater flexibility and probably far higher speed, for example if using multiple regular expressions within a template.
  • added 4 string generators for
    • RSYSLOG_FileFormat
    • RSYSLOG_TraditionalFileFormat
    • RSYSLOG_ForwardFormat
    • RSYSLOG_TraditionalForwardFormat
  • bugfix: mutexes used to simulate atomic instructions were not destructed
  • bugfix: regression caused more locking action in msg.c than necessary
  • bugfix: “$ActionExecOnlyWhenPreviousIsSuspended on” was broken
  • bugfix: segfault on HUP when “HUPIsRestart” was set to “on” thanks varmojfekoj for the patch
  • bugfix: default for $OMFileFlushOnTXEnd was wrong (“off”).

This, in default mode, caused buffered writing to be used, what means that it looked like no output were written or partial lines. Thanks to Michael Biebl for pointing out this bug.

Scroll to top