rsyslog 7.4.2 (v7-stable)
Download file name: rsyslog 7.4.2 (stable)
rsyslog 7.4.2 (stable)
sha256 hash:
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 7.4.2 File size: 2906942 bytes
rsyslog 7.4.1 (v7-stable) released
This is a maintenance release, consisting primarily of bug fixes. Note that imjournal was extended to support rate-limiting, as this is needed as a safeguard for problems in systemd journal which in turn caused grief to rsyslog. See Rainer’s blog posting for more details:
http://blog.gerhards.net/2013/
ChangeLog:
http://www.rsyslog.com/changelog-for-7-4-1-v7-stable/
Download:
http://www.rsyslog.com/rsyslog-7-4-1-v7-stable/
As always, feedback is appreciated.
Best regards,
Florian Riedl
Changelog for 7.4.1 (v7-stable)
Version 7.4.1 [v7.4-stable] 2013-06-17
- imjournal: add ratelimiting capability
The original imjournal code did not support ratelimiting at all. We now have our own ratelimiter. This can mitigate against journal database corruption, when the journal re-sends old data. This is a current bug in systemd journal, but we won’t outrule this to happen in the future again. So it is better to have a safeguard in place. By default, we permit 20,000 messages witin 10 minutes. This may be a bit restrictive, but given the risk potential it seems reasonable.
Users requiring larger traffic flows can always adjust the value. - bugfix: potential loop in rate limiting
if the message that tells about rate-limiting gets rate-limited itself, it will potentially create and endless loop - bugfix: potential segfault in imjournal if journal DB is corrupted
- bugfix: prevent a segfault in imjournal if state file is not defined
- bugfix imzmq3: potential segfault on startup
if no problem happend at startup, everything went fine
Thanks to Hongfei Cheng and Brian Knox for the patch
rsyslog 7.4.1 (v7-stable)
Download file name: rsyslog 7.4.1 (stable)
rsyslog 7.4.1 (stable)
sha256 hash: f890b56fc5122fabf79994e11bdefb
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 7.4.1 File size: 2.902 MB
rsyslog 7.4.0 (v7-stable) released
This is the first release of the 7.4 stable branch. It incorporates all new features from the 7.3 development branch. For details, see the blog posting http://www.rsyslog.com/7-4-0-the-new-stable/
ChangeLog: http://www.rsyslog.com/changelog-for-7-4-0-v7-stable/
Download: http://www.rsyslog.com/rsyslog-7-4-0-v7-stable/
As always, feedback is appreciated.
Best regards, Florian Riedl
7.4.0 – the new stable
new rsyslog 7.4.0 stable released
We just released rsyslog 7.4.0, a new stable release which replaces the 7.2 branch. After nine month of hard work, there are many exciting enhancements compared to 7.2, and I thought I give you a quick rundown of the more important new features. Note that while I list some “minor features” at the end of this posting, the list is not complete. I left out those things that are primarily of interest for smaller groups of users. So if you look for a specific feature not mentioned here, it may pay to look at the ChangeLog or post a question to the rsyslog mailing list.
With this release, the rsyslog project officially supports the 7.4 and 7.2 branches. If support for older versions is required, utilizing Adiscon’s professional services for rsyslog is recommended.
Note that I only list main headlines for each of the features. Follow links (where provided) to gain more in-depth information.
Security Package
- introduction of Linux-like rate-limiting for all inputs
- “Last message repeated n times” now done on a per-input basis; makes it much more useful AND increases processing speed.
- omjournal writes messages to the journal
- imjournal obtains messages including journal-specific meta data items from the journal
Performance Improvements
- Disk Queue Performance greatly improved
- DNS chache greatly improved and optimized
- omfile now supports fully async writing
- script optimizer now changes frequently-used long-running filters into equivalent quick ones when possible (this even affects some distros default configs and is a great performance saver)
Minor Features
- various plugins now support the new RainerScript based config language
- omlibdbi improvements, among them support for transactions
- ommysql now supports transactions
- improved omfile zip writing speed
- performance optimizations
- omelasticsearch improvements (bulk processing mode, local error file)
- omudpspoof now supports packets larger than 1472 by using fragmentation
- omrelp now supports session timeout
- contributed module (not project-supported) omrabbitmq was added
Changelog for 7.4.0 (v7-stable)
Version 7.4.0 [v7.4-stable] 2013-06-06
This starts a new stable branch based on 7.3.15 plus the following changes:
- add –enable-cached-man-pages ./configure option
permits to build rsyslog on a system where rst2man is not installed. In that case, cached versions of the man pages are used (they were built during “make dist”, so they should be current for the version in question. - doc bugfix: ReadMode wrong in imfile doc, two values were swapped
Thanks to jokajak@gmail.com for mentioning this
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=450 - imjournal: no longer do periodic wakeup
- bugfix: potential hang *in debug mode* on rsyslogd termination
This ONLY affected rsyslogd if it were running with debug output enabled. - bugfix: $template statement with multiple spaces lead to invalid tpl name
If multiple spaces were used in front of the template name, all but one of them became actually part of the template name. So $template a,”…” would be name ” a”, and as such “a” was not available, e.g. in
*.* /var/log/file;a
This is a legacy config problem. As it was unreported for many years, no backport of the fix to old versions will happen. This is a long-standing bug that was only recently reported by forum user mc-sim.
Reference: http://kb.monitorware.com/post23448.html - 0mq fixes; credits to Hongfei Cheng and Brian Knox
rsyslog 7.4.0 (v7-stable)
Download file name: rsyslog 7.4.0 (stable)
rsyslog 7.4.0 (stable)
sha256 hash: a9e7badab4f34df3543deb3f82a4cdffcfaa51f4d0a26342dfc6b14945eb00cb
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 7.4.0 File size: 2.900 MB
Changelog for 7.2.7 (v7-stable)
Version 7.2.7 [v7-stable] 2013-04-17
- rsyslogd startup information is now properly conveyed back to init
when privileges are beging dropped
Actually, we have moved termination of the parent in front of the
priv drop. So it shall work now in all cases. See code comments in
commit for more details. - If forking, the parent now waits for a maximum of 60 seconds for
termination by the child - improved debugging support in forked (auto-backgrounding) mode
The rsyslog debug log file is now continued to be written across the
fork. - updated systemd files to match current systemd source
- bugfix: failover/action suspend did not work correctly
This was experienced if the retry action took more than one second
to complete. For suspending, a cached timestamp was used, and if the
retry took longer, that timestamp was already in the past. As a
result, the action never was kept in suspended state, and as such
no failover happened. The suspend functionalit now does no longer use
the cached timestamp (should not have any performance implication, as
action suspend occurs very infrequently). - bugfix: nested if/prifilt conditions did not work properly
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=415 - bugfix: script == comparison did not work properly on JSON objects
[backport from 7.3 branch] - bugfix: imudp scheduling parameters did affect main thread, not imudp
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=409 - bugfix: imuxsock rate-limiting could not be configured via legacy conf
Rate-limiting for the system socket could not be configured via legacy
configuration directives. However, the new-style RainerScript config
options worked.
Thanks to Milan Bartos for the patch.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=390 - bugfix: using group resolution could lead to endless loop
Thanks to Tomas Heinrich for the patch.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=310 - bugfix: $mmnormalizeuseramsg paramter was specified with wrong type
Thank to Renzhong Zhang for alerting us of the problem.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=420 - bugfix: RainerScript getenv() function caused segfault when var was
not found.
Thanks to Philippe Muller for the patch. - bugfix: several issues in imkmsg
see bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=421#c8 - bugfix: imuxsock was missing SysSock.ParseTrusted module parameter
To use that functionality, legacy rsyslog.conf syntax had to be used.
Also, the doc was missing information on the “ParseTrusted” set of
config directives. - bugfix: parameter action.execOnlyWhenPreviousIsSuspended was accidently
of integer-type. For obvious reasons, it needs to be boolean. Note
that this change can break existing configurations if they circumvented
the problem by using 0/1 values. - doc bugfix: rsyslog.conf man page had invalid file format info
rsyslog 7.2.7 (v7-stable) released
We have just released 7.2.7 of the v7 stable branch. This is a pure bug-fixing release. More information on the changes can be found in the ChangeLog.