rsyslog

rsyslog 4.6.2 (v4-stable) released

Hi all,

We have just released rsyslog 4.6.2, a member of the v4-stable branch. This is a bug-fixing release containing some important fixes and also two new features. It is a recommended update for all users of the v4-stable. See Changelog for more details.

ChangeLog:

http://www.rsyslog.com/Article449

Download:

http://www.rsyslog.com/Downloads-req-viewdownloaddetails-lid-198.phtml

As always, feedback is appreciated.

Best regards,
Tom Bergfeld

Changelog for 5.4.0 (v5-stable)

Version 5.4.0 [v5-stable] (rgerhards), 2010-03-08
***************************************************************************
This is a new stable v5 version. It contains all fixes and enhancements
made during the 5.3.x phase as well as those listed below. Note that the 5.2.x series was quite buggy and as such all users are strongly advised to upgrade to 5.4.0.
***************************************************************************

  • bugfix: omruleset failed to work in many cases
    bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=179
    Thanks to Ryan B. Lynch for reporting this issue.
  • 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
    [merged in from v3.22.2]

ChangeLog for 4.6.1 (v4-stable)

Version 4.6.1 [v4-stable] (rgerhards), 2010-03-04

  • re-enabled old pipe output (using new module ompipe, built-in) after some problems with pipes (and especially in regard to xconsole) were discovered.
    Thanks to Michael Biebl for reporting the issues.

  • bugfix: potential problems with large file support could cause segfault … and other weird problems. This seemed to affect 32bit-platforms only, but I can not totally outrule there were issues on other platforms as well. The previous code could cause system data types to be defined inconsistently, and that could lead to various troubles.
    Special thanks go to the Mandriva team for identifying an initial problem, help discussing it and ultimately a fix they contributed.

  • bugfix: fixed problem that caused compilation on FreeBSD 9.0 to fail.
    bugtracker: http://bugzilla.adiscon.com/show_bug.cgi?id=181
    Thanks to Christiano for reporting.

  • bugfix: potential segfault in omfile when a dynafile open failed
    In that case, a partial cache entry was written, and some internal pointers (iCurrElt) not correctly updated. In the next iteration, that could lead to a segfault, especially if iCurrElt then points to the then-partial record. Not very likely, but could happen in practice.

  • bugfix (theoretical): potential segfault in omfile under low memory condition. This is only a theoretical bug, because it would only happen when strdup() fails to allocate memory – which is highly unlikely and will probably lead to all other sorts of errors.
  • bugfix: comment char (‘#’) in literal terminated script parsing and thus could not be used. bugtracker: http://bugzilla.adiscon.com/show_bug.cgi?id=119
    [merged in from v3.22.2]

syslog 4.6.1 (v4-stable) released

Hi all,
We have just released rsyslog 4.6.1.

Rsyslog 4.6.1 is a bug fixing release. Most importantly, it fixes an issue with the build system that could potentially result in segfaults, especially on 32 bit machines. Please review the ChangeLog for details.

This is a recommended update for all v4-stable users.

ChangeLog:

http://www.rsyslog.com/Article445

Download:

http://www.rsyslog.com/Downloads-req-viewdownloaddetails-lid-196.phtml

As always, feedback is appreciated.

Best regards,
Tom Bergfeld

ChangeLog for 4.6.0 (v4-beta)

Version 4.6.0 [v4-stable] (rgerhards), 2010-02-24

***************************************************************************

This is a new stable v4 version. It contains all fixes and enhancements
made during the 4.5.x phase as well as those listed below.

Note: this version is scheduled to conclude the v4 development process.
Do not expect any more new developments in v4. The focus is now
on v5 (what also means we have a single devel branch again).

(“development” means new feature development, bug fixes are of
course provided for v4-stable)
***************************************************************************

  • improved testbench to contain samples for totally malformed messages which miss parts of the message content
  • bugfix: some malformed messages could lead to a missing LF inside files or some other missing parts of the template content.
  • bugfix: if a message ended immediately with a hostname, the hostname was mistakenly interpreted as TAG, and localhost be used as hostname
  • bugfix: message without MSG part could case a segfault [backported from v5 commit 98d1ed504ec001728955a5bcd7916f64cd85f39f]. This actually was a “recent” regression, but I did not realize that it was introduced by the performance optimization in v4-devel. Shame on me for having two devel versions at the same time…

rsyslog 4.6.0 (v4-stable) released

Hi all,
We have just released rsyslog 4.6.0.

Rsyslog 4.6.0 is the next revision of the v4-stable branch. It brings all new features of 4.5.x to the stable releases. This includes bug fixes as well as many new features. Out of the many, I would like to highlight the ability to have output files automatically zipped, multiple TCP listeners and overall performance improvement. For all details, please check the 4.5.x change log entries.

This release has undergone rigorous testing in some very demanding environments. We held release until all tests went out well. We are happy to have reached this stage now and sincerely think that the version is ready for prime time. Thanks to everyone who contributed test time and bug reports!

We recommend that all v4-stable users have a look at 4.6.0 and consider updating to it. Please note that 4.6.0 also does have some patches which 4.4.2 does not have. Support for 4.4.2 is concluded now (but still available via support contracts).

ChangeLog:

http://www.rsyslog.com/Article443

Download:

http://www.rsyslog.com/Downloads-req-viewdownloaddetails-lid-195.phtml

As always, feedback is appreciated.

Best regards,
Tom Bergfeld

On the Use of English

I ventured to write this book in English because …
it will be more easily read in poor English,
than in good German by 90% of my intended readers.
— HANS J. STETTER, Analysis of Discretization Methods for
Ordinary Differential Equations (1973)

There is not much I could add to Mr. Stetter’s thought, except, maybe, that the number to quote probably tends more to 99% in this case than to the 90% Mr. Stetter notes. So please pardon those errors in language use that I have not yet been able to fix or even see. Suggestions for corrections and improvements are always welcome.

Scroll to top