Changelog for 7.2.3 (v7-stable)
Version 7.2.3 [v7-stable] 2012-11-21
- regression fix: rsyslogd terminated when wild-card $IncludeConfig did not
find actual include files. For example, if this directive is present:
$IncludeConfig /etc/rsyslog.d/*.conf
and there are no *.conf files in /etc/rsyslog.d (but rsyslog.d exists),
rsyslogd will emit an error message and terminate. Previous (and expected)
behaviour is that an empty file set is no problem. HOWEVER, if the
directory itself does not exist, this is flagged as an error and will
load to termination (no startup).
Unfortunately, this is often the case by default in many distros, so this
actually prevents rsyslog startup.
rsyslog 7.2.2 (v7-stable)
Download file name: rsyslog 7.2.2 (stable)
rsyslog 7.2.2 (stable)
sha256 hash: 9b407b9cd7069081c553f69ada6a3246c822ffc0c53a05e14af096e6b50c9333
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 7.2.2 File size: 2.615 MB
rsyslog 7.3.3 (v7-devel) released
We have just released 7.3.3 of the v7-devel branch. This release most importantly provides increased performance for the disk queue subsystem. Especially CPU-use will be much lower when unspooling disk queues. It also contains all known fixes for v7, some imported from v7-stable and earlier versions.
ChangeLog:
http://www.rsyslog.com/changelog-for-7-3-3-v7-devel/
Download:
http://www.rsyslog.com/rsyslog-7-3-3-v7-devel/
As always, feedback is appreciated.
Best regards,
Florian Riedl
Changelog for 7.3.3 (v7-devel)
Version 7.3.3 [devel] 2012-11-07
- improved disk queue performance
- bugfix: dynafile zip files could be corrupted
This could happen if a dynafile was destructed before the first write. In practice, this could happen if few lines were written to a file and it then became evicted from the dynafile cache. This would probably look very random, because it depended on the timing in regard to message volume and dynafile cache size.
rsyslog 7.3.3 (v7-devel)
Download file name: rsyslog 7.3.3 (devel)
rsyslog 7.3.3 (devel)
sha256 hash: c00f4c79a5502af232466ef7c21191868ec7a25e8da9e54255988ca0f579ee47
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 7.3.3 File size: 2.716 MB
rulesets and rsyslog 7.2+
In rsyslog 7.2.0 we introduced some interesting config enhancements. Among these are changes to how rulesets can be specified or called. A ruleset is basically looking like this:
ruleset(name="rulesetname") { statements here }
As you can see, you specify a ruleset by its name. All statements that will be specified go into the curly brackets. In addition, a ruleset can be called by another ruleset. This is simply done by call
rulesetname
The rulesetname is just plainly specified. We hope this to be more intuitively. Here is a larger example (bascially taken from the rsyslog mailing list, thanks to Brian Knox). module(load="imptcp" keepalive="on")
# use imptcp just as example for bind ruleset below ruleset(name="rs1") {
*.* /var/log/test1.log } ruleset(name="rs2") { *.* /var/log/test2.log call rs1 } input(type="imptcp" port="13514" ruleset="rs2")
All statements, which are NOT specified in a ruleset will be automatically inserted into the default ruleset.
Legacy $Ruleset statements are still supported, but cannot be cross-used with the new ruleset() statements.
rsyslog 7.3.2 (v7-devel) released
This release introduced a totally new rate-limiting system for all modules as well as much better “last message repeated n times” handling. For details, please see Rainer’s blog at
http://blog.gerhards.net/2012/10/rate-limiting-in-rsyslog-732.html
Besides this feature, the version also includes enhancements for omelasticsearch as well as input batching support for imudp (which should provide some performance boost on very busy systems). Also, action-like statements (call, stop, …) are now supported in action lists. Of course, there are also some bugfixes, many imported from v6 and v7.2.
ChangeLog:
http://www.rsyslog.com/changelog-for-7-3-2-v7-devel/
Download:
http://www.rsyslog.com/rsyslog-7-3-2-v7-devel/
As always, feedback is appreciated.
Best regards,
Tim Eifler
Changelog for 7.3.2 (v7-devel)
Version 7.3.2 [devel] 2012-10-30
- totally reworked ratelimiting and “last message repeated n times”
all over rsyslog code. Each of the supported inputs now supports
linux-like ratelimiting (formerly only imuxsock did). Also, the
“last message repeated n times” is now processed at the input side
and no longer at the output side of rsyslog processing. This
provides the basis for new future additions as well as usually more
performance and a much simpler output part (which can be even further
refactored). - imtcp: support for Linux-Type ratelimiting added
- imptcp: support for Linux-Type ratelimiting added
- imudp enhancements:
- support for input batching added (performance improvement)
- support for Linux-Type ratelimiting added
- permited action-like statements (stop, call, …) in action lists
- bugfix: segfault on startup when modules using MSG_PASSING mode are used
- omelasticsearch: support for writing data errors to local file added
- omelasticsearch: fix check for bulk processing status response
rsyslog 7.3.2 (v7-devel)
Download file name: rsyslog 7.3.2 (devel)
rsyslog 7.3.2 (devel)
sha256 hash: 7b3918f158aa1bf4f3481ffce4075c69b48a44cf0da17bc6735cb4247b17615b
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 7.3.2 File size: 2.628 MB
rsyslog 7.2.1 (v7-stable) released
We have just released 7.2.1 of the v7 stable branch. This is a pure bug-fixing release. More information on the changes can be found in the ChangeLog.
ChangeLog:
http://www.rsyslog.com/changelog-for-7-2-1-v7-stable/
Download:
http://www.rsyslog.com/rsyslog-7-2-1-v7-stable/
As always, feedback is appreciated.
Best regards,
Tim Eifler