rsyslog 5.8.12 (v5-stable) released
This is primarily a maintenance release. It includes several bugfixes for omudpspoof, debugging or disk queues as well as other fixes. For more details, please review the changelog.
ChangeLog:
http://www.rsyslog.com/changelog-for-5-8-12-v5-stable/
Download:
http://www.rsyslog.com/rsyslog-5-8-12-v5-stable/
As always, feedback is appreciated.
Best regards,
Florian Riedl
Changelog for 5.8.12 (v5-stable)
Version 5.8.12 [V5-stable] 2012-06-06
- add small delay (50ms) after sending shutdown message
There seem to be cases where the shutdown message is otherwise not processed, not even on an idle system.
Thanks to Marcin for bringing this problem up. - support for resolving huge groups
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=310
Thanks to Alec Warner for the patch - bugfix: delayble source could block action queue, even if there was a disk queue associated with it. The root cause of this problem was that it makes no sense to delay messages once they arrive in the action queue – the “input” that is being held in that case is the main queue worker, what makes no sense.
Thanks to Marcin for alerting us on this problem and providing instructions to reproduce it. - bugfix: disk queue was not persisted on shutdown, regression of fix to
http://bugzilla.adiscon.com/show_bug.cgi?id=299
The new code also handles the case of shutdown of blocking light and full delayable sources somewhat smarter and permits, assuming sufficient timeouts, to persist message up to the max queue capacity. Also some nits in debug instrumentation have been fixed. - bugfix/omudpspoof: problems, including abort, happend when run on multiple threads. Root cause is that libnet is not thread-safe. omudpspoof now guards libnet calls with their own mutex.
- bugfix: if debug message could end up in log file when forking if rsyslog was set to auto-background (thus fork, the default) and debug mode to stdout was enabled, debug messages ended up in the first log file opened. Currently, stdout logging is completely disabled in forking mode (but writing to the debug log file is still possible). This is a change in behaviour, which is under review. If it causes problems to you, please let us know.
Thanks to Tomas Heinrich for the patch. - bugfix/tcpflood: sending small test files did not work correctly
- bugfix: potential hang due to mutex deadlock
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=316
Thanks to Andreas Piesk for reporting&analyzing this bug as well as providing patches and other help in resolving it. - bugfix: property PROCID empty instead of proper nilvalue if not present
If it is not present, it must have the nilvalue “-” as of RFC5424
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=332
Thanks to John N for reporting this issue.
rsyslog 5.8.12 (v5-stable)
Download file name: rsyslog 5.8.12 (stable)
rsyslog 5.8.12 (stable)
md5sum: e4a105a004ca7113ec5948b30c6af20c
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 5.8.12 File size: 2.393 MB
rsyslog 6.3.10 (v6-beta) released
This is a new beta release vor the v6 branch. It only contains bugfixes for several features and general behaviour. For more details, please take a look into the ChangeLog.
ChangeLog:
http://www.rsyslog.com/changelog-for-6-3-10-v6-beta/
Download:
http://www.rsyslog.com/rsyslog-6-3-10-beta/
As always, feedback is appreciated.
Best regards,
Florian Riedl
rsyslog 6.3.10 (beta)
Download file name: rsyslog 6.3.10 (beta)
rsyslog 6.3.10 (beta)
md5sum: 9df95c31c89e5b0c10cbcaff5995225d
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 6.3.10 File size: 2.52 MB
Changelog for 6.3.10 (v6-beta)
Version 6.3.10 [BETA] 2012-06-04
- bugfix: delayble source could block action queue, even if there was disk queue associated with it. The root cause of this problem was that it makes no sense to delay messages once they arrive in the action queue – the “input” that is being held in that case is the main queue worker, what makes no sense.
Thanks to Marcin for alerting us on this problem and providing instructions to reproduce it. - bugfix: invalid free in imptcp could lead to abort during startup
- bugfix: if debug message could end up in log file when forking if rsyslog was set to auto-background (thus fork, the default) and debug mode to stdout was enabled, debug messages ended up in the first log file opened. Currently, stdout logging is completely disabled in forking mode (but writing to the debug log file is still possible). This is a change in behaviour, which is under review. If it causes problems to you, please let us know.
Thanks to Tomas Heinrich for the patch. - bugfix: –enable-smcustbindcdr configure directive did not work
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=330
Thanks to Ultrabug for the patch. - bugfix: made rsyslog compile when libestr ist not installed in /usr
Thanks to Miloslav Trmač for providing patches and suggestions
rsyslog 6.3.9 (v6-beta) released
This is a new beta release vor the v6 branch. It is a follow-up to the current devel-branch. This release contains a lot of bugfixes and has some new features added like the capability to specify substrings for field extraction mode or the new property “jsonf”. More detailed information can be found in the changelog.
Since this is a new beta version, it would be nice to get some test results on the features and fixes from the userbase. Responses can be submitted via the mailing list.
ChangeLog:
http://www.rsyslog.com/changelog-for-6-3-9-v6-beta/
Download:
http://www.rsyslog.com/rsyslog-6-3-9-beta/
As always, feedback is appreciated.
Best regards,
Florian Riedl
rsyslog 6.3.9 (beta)
Download file name: rsyslog 6.3.9 (beta)
rsyslog 6.3.9 (beta)
md5sum: f126f7a432a3f68ea52a2cbce447d798
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 6.3.9 File size: 2.52 MB
Changelog for 6.3.9 (v6-beta)
Version 6.3.9 [BETA] 2012-05-22
- bugfix: imtcp could cause hang during reception this also applied to other users of core file tcpsrv.c, but imtcp was by far the most prominent and widely-used, the rest rather exotic (like imdiag)
- added capability to specify substrings for field extraction mode
- added the “jsonf” property replacer option (and fieldname)
- bugfix: omudpspoof did not work correctly if no spoof hostname was configured
- bugfix: property replacer option “json” could lead to content loss message was truncated if escaping was necessary
- bugfix: assigned ruleset was lost when using disk queues
This looked quite hard to diagnose for disk-assisted queues, as the pure memory part worked well, but ruleset info was lost for messages stored inside the disk queue. - bugfix/imuxsock: solving abort if hostname was not set; configured hostname was not used (both merge regressions)
- bugfix/omfile: template action parameter was not accepted (and template name set to “??” if the parameter was used)
Thanks to Brian Knox for alerting us on this bug. - bugfix: ommysql did not properly init/exit the mysql runtime library this could lead to segfaults. Triggering condition: multiple action instances using ommysql. Thanks to Tomas Heinrich for reporting this problem and providing an initial patch (which my solution is based on, I need to add more code to clean the mess up).
- bugfix: rsyslog did not terminate when delayable inputs were blocked due to unvailable sources. Fixes:
http://bugzilla.adiscon.com/show_bug.cgi?id=299
Thanks to Marcin M for bringing up this problem and Andre Lorbach for helping to reproduce and fix it. - added capability to specify substrings for field extraction mode
- bugfix: disk queue was not persisted on shutdown, regression of fix to
http://bugzilla.adiscon.com/show_bug.cgi?id=299
The new code also handles the case of shutdown of blocking light and full delayable sources somewhat smarter and permits, assuming sufficient timouts, to persist message up to the max queue capacity. Also some nits in debug instrumentation have been fixed.
Changelog for 6.2.1 (v6-stable)
Version 6.2.1 [v6-stable], 2012-05-10
- change plugin config interface to be compatible with pre-v6.2 system
The functionality was already removed (because it is superseeded by the
v6.3+ config language), but code was still present. I have now removed
those parts that affect interface. Full removal will happen in v6.3, in
order to limit potential regressions. However, it was considered useful
enough to do the interface change in v6-stable; this also eases merging
branches! - re-licensed larger parts of the codebase under the Apache license 2.0
- bugfix: omprog made rsyslog abort on startup if not binary to
execute was configured - bugfix: imklog invalidly computed facility and severity
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=313 - bugfix: stopped DA queue was never processed after a restart due to a
regression from statistics module - bugfix: memory leak in array passing output module mode
- bugfix: ommysql did not properly init/exit the mysql runtime library
this could lead to segfaults. Triggering condition: multiple action
instances using ommysql. Thanks to Tomas Heinrich for reporting this
problem and providing an initial patch (which my solution is based on,
I need to add more code to clean the mess up). - bugfix: rsyslog did not terminate when delayable inputs were blocked
due to unvailable sources. Fixes:
http://bugzilla.adiscon.com/show_bug.cgi?id=299
Thanks to Marcin M for bringing up this problem and Andre Lorbach
for helping to reproduce and fix it. - bugfix/tcpflood: sending small test files did not work correctly