rsyslog

The rocket-fast system for log processing

v5

rsyslog 5.8.3 (v5-stable) released

By adisconteamPosted on Posted in News, Release AnnouncementTagged , , , ,

This release adds support for new systemd features as well as some forward-compatibility patches. Note that the syntax of the outchannel action has slightly changed. The previous syntax is still accepted, but a warning message describing the new syntax is issued.

ChangeLog:

http://www.rsyslog.com/changelog-for-5-8-3-v5-stable/

Download:

http://www.rsyslog.com/rsyslog-5-8-3-v5-stable/

As always, feedback is appreciated.

Best regards,
Tom Bergfeld

Changelog for 5.8.3 (v5-stable)

By adisconteamPosted on Posted in ChangelogTagged , , ,

Version 5.8.3 [V5-stable] (rgerhards), 2011-07-11

  • systemd support: set stdout/stderr to null – thx to Lennart for the patch
  • added support for the “:omusrmsg:” syntax in configuring user messages
  • added support for the “:omfile:” syntax in configuring user messages
    Note: previous outchannel syntax will generate a warning message. This
    may be surprising to some users, but it is quite urgent to alert them
    of the new syntax as v6 can no longer support the previous one.

rsyslog 5.9.1 (devel) released

By adisconteamPosted on Posted in News, Release AnnouncementTagged , , ,

This release offers better systemd integration as well as better support for chrooted environments by supporting better timestamps in these environments. It also contains a number of important bug fixes.
Upgrading to this release is strongly recommended for users of the v5-devel branch.

Remeber that v5-devel receives mostly minor and/or very urgent improvements. The “real” development takes place in v6, which already offers features not found in v5.

ChangeLog:

http://www.rsyslog.com/changelog-for-5-9-1-v5-devel/

Download:

http://www.rsyslog.com/rsyslog-5-9-1-devel/

As always, feedback is appreciated.

Best regards,
Tom Bergfeld

Changelog for 5.9.1 (v5-devel)

By adisconteamPosted on Posted in ChangelogTagged , ,

Version 5.9.1 [V5-DEVEL] (rgerhards), 2011-06-30

  • added support for obtaining timestamp for kernel message from message
    If the kernel time-stamps messages, time is now take from that
    timestamp instead of the system time when the message was read. This
    provides much better accuracy. Thanks to Lennart Poettering for
    suggesting this feature and his help during implementation.

  • added support for obtaining timestamp from system for imuxsock
    This permits to read the time a message was submitted to the system
    log socket. Most importantly, this is provided in microsecond resolution.
    So we are able to obtain high precision timestampis even for messages
    that were – as is usual – not formatted with them. This also simplifies
    things in regard to local time calculation in chroot environments.
    Many thanks to Lennart Poettering for suggesting this feature,
    providing some guidance on implementing it and coordinating getting the
    necessary support into the Linux kernel.

  • bugfix: timestamp was incorrectly calculated for timezones with minute
    offset
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=271

  • bugfix: problems in failover action handling
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=270
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=254

  • bugfix: mutex was invalidly left unlocked during action processing
    At least one case where this can occur is during thread shutdown, which
    may be initiated by lower activity. In most cases, this is quite
    unlikely to happen. However, if it does, data structures may be
    corrupted which could lead to fatal failure and segfault. I detected
    this via a testbench test, not a user report. But I assume that some
    users may have had unreproducable aborts that were cause by this bug.

  • bugfix: memory leak in imtcp & subsystems under some circumstances
    This leak is tied to error conditions which lead to incorrect cleanup
    of some data structures. [backport from v6]

  • bugfix/improvement:$WorkDirectory now gracefully handles trailing slashes

rsyslog 5.8.2 (v5-stable) released

By adisconteamPosted on Posted in News, Release AnnouncementTagged , , , ,

This is a maintenance release containing only stability updates.
Note that the mutex-related bug can have quite fatal consequences. So it is highly recommended to upgrade to this version, even if you did not yet experience any problems.

ChangeLog:

http://www.rsyslog.com/changelog-for-5-8-2-v5-stable/

Download:

http://www.rsyslog.com/rsyslog-5-8-2-v5-stable/

As always, feedback is appreciated.

Best regards,
Tom Bergfeld

Changelog for 5.8.2. (v5-stable)

By adisconteamPosted on Posted in ChangelogTagged , , , ,

Version 5.8.2 [V5-stable] (rgerhards), 2011-06-21

  • bugfix: problems in failover action handling
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=270
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=254

  • bugfix: mutex was invalidly left unlocked during action processing
    At least one case where this can occur is during thread shutdown, which
    may be initiated by lower activity. In most cases, this is quite
    unlikely to happen. However, if it does, data structures may be
    corrupted which could lead to fatal failure and segfault. I detected
    this via a testbench test, not a user report. But I assume that some
    users may have had unreproducable aborts that were cause by this bug.

  • bugfix: memory leak in imtcp & subsystems under some circumstances
    This leak is tied to error conditions which lead to incorrect cleanup
    of some data structures. [backport from v6]

  • bugfix/improvement:$WorkDirectory now gracefully handles trailing slashes

Changelog for 5.9.0 (v5-devel)

By adisconteamPosted on Posted in ChangelogTagged , , , ,

Version 5.9.0 [V5-DEVEL] (rgerhards), 2011-06-08

  • imfile: added $InputFileMaxLinesAtOnce directive
  • enhanced imfile to support input batching
  • added capability for imtcp and imptcp to activate keep-alive packets
    at the socket layer. This has not been added to imttcp, as the latter is
    only an experimental module, and one which did not prove to be useful.
    reference: http://kb.monitorware.com/post20791.html

  • added support to control KEEPALIVE settings in imptcp
    this has not yet been added to imtcp, but could be done on request.

  • $ActionName is now also used for naming of queues in impstats
    as well as in the debug output

  • bugfix: do not open files with full privileges, if privs will be dropped
    This make the privilege drop code more bulletproof, but breaks Ubuntu’s
    work-around for log files created by external programs with the wrong
    user and/or group. Note that it was long said that this “functionality”
    would break once we go for serious privilege drop code, so hopefully
    nobody still depends on it (and, if so, they lost…).

  • bugfix: pipes not opened in full priv mode when privs are to be dropped
  • this begins a new devel branch for v5
  • better handling of queue i/o errors in disk queues. This is kind of a
    bugfix, but a very intrusive one, this it goes into the devel version
    first. Right now, “file not found” is handled and leads to the new
    emergency mode, in which disk action is stopped and the queue run
    in direct mode. An error message is emited if this happens.

  • added support for user-level PRI provided via systemd
  • added new config directive $InputTCPFlowControl to select if tcp
    received messages shall be flagged as light delayable or not.

  • enhanced omhdfs to support batching mode. This permits to increase
    performance, as we now call the HDFS API with much larger message
    sizes and far more infrequently

  • bugfix: failover did not work correctly if repeated msg reduction was on
    affected directive was: $ActionExecOnlyWhenPreviousIsSuspended on
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=236

Scroll to top