Rsyslog Windows Agent 1.1 Released
Adiscon is proud to announce the 1.1 release of RSyslog Windows Agent. This is a minor release. This release contains new feature as well as a bugfix for the SNMP Trap Receiver. For more details read the Changelog. Build-IDs: Service 1.1.105, Client 1.1.119
Features |
|
Bugfixes |
|
Version 1.1 is a free download. Customers with existing 1.x keys can contact our Sales department for upgrade prices. If you have a valid Upgrade Insurance ID, you can request a free new key by sending your Upgrade Insurance ID to sales@adiscon.com. Please note that the download enables the free 30-day trial version if used without a key – so you can right now go ahead and evaluate it.
Changelog for 6.5.0 (v6-devel)
Version 6.5.0 [devel] 2012-08-28
- imrelp now supports non-cancel thread termination
(but now requires at least librelp 1.0.1) - implemented freeCnf() module interface
This was actually not present in older versions, even though some modules already used it. The implementation was now done, and not in 6.3/6.4 because the resulting memory leak was ultra-slim and the new interface handling has some potential to seriously break things. Not the kind of thing you want to add in late beta state, if avoidable. - added –enable-debugless configure option for very high demanding envs
This actually at compile time disables a lot of debug code, resulting in some speedup (but serious loss of debugging capabilities) - added new 0mq plugins (via czmq lib)
Thanks to David Kelly for contributing these modules - bugfix: omhdfs did no longer compile
- bugfix: SystemLogSocketAnnotate did not work correctly
Thanks to Miloslav Trmač for the patch - $SystemLogParseTrusted config file option
Thanks to Milan Bartos for the patch - added template config directive
- added new uuid message property
Thanks to Jérôme Renard for the idea and patches.
Note: patches were released under ASL 2.0, see
http://bugzilla.adiscon.com/show_bug.cgi?id=353
rsyslog 5.10.0 (v5-stable) released
We just released 5.10.0 of the v5-stable branch. This is the new rsyslog v5-stable, incorporating all changes from the 5.9.x series. In addition to that, it contains the fixes and enhancements listed in the ChangeLog.
ChangeLog:
http://www.rsyslog.com/changelog-for-5-10-0-v5-stable/
Download:
http://www.rsyslog.com/rsyslog-5-10-0-v5-stable/
As always, feedback is appreciated.
Best regards,
Florian Riedl
Changelog for 5.10.0 (v5-stable)
Version 5.10.0 [V5-STABLE], 2012-08-23
NOTE: this is the new rsyslog v5-stable, incorporating all changes from the 5.9.x series. In addition to that, it contains the fixes and enhancements listed below in this entry.
- 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 timouts, to persist message up to the max queue capacity. Also some nits in debug instrumentation have been fixed. - 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: 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. - bugfix: “last message repeated n times” message was missing hostname
Thanks to Zdenek Salvet for finding this bug and to Bodik for reporting - bugfix: multiple main queues with same queue file name was not detected
This lead to queue file corruption. While the root cause is a config error, it is a bug that this important and hard to find config error was not detected by rsyslog.
rsyslog 5.8.13 (v5-stable) released
We just released 5.8.13 of the v5-stable branch. This is primarily a maintenance release. It includes several bugfixes for potential aborts or DA queues as well as other fixes. For more details, please review the ChangeLog.
This is the last release of 5.8.x to get the latest patches into this stable version. Soon we will release 5.10.1 which should be the version to be used if you are following the stable releases.
ChangeLog:
http://www.rsyslog.com/changelog-for-5-8-13-v5-stable/
Download:
http://www.rsyslog.com/rsyslog-5-8-13-v5-stable/
As always, feedback is appreciated.
Best regards,
Florian Riedl
rsyslog 5.8.13 (v5-stable)
Download file name: rsyslog 5.8.13 (stable)
rsyslog 5.8.13 (stable)
md5sum: 8d228a8b622f90b320c95f38be7fc5bb
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 5.8.13 File size: 2.394 MB
rsyslog 6.4.0 (v6-stable) released
This is the first version of the 6.4.x stable branch. It inherits all patches that were introduced in the 6.3.x beta branch. It is the new successor of the 6.2.x stable branch. As of now, the 6.3.x beta is finished as well.
For more information about the fixes, please refer to the ChangeLog.
ChangeLog:
http://www.rsyslog.com/changelog-for-6-4-0-v6-stable/
Download:
http://www.rsyslog.com/rsyslog-6-4-0-v6-stable/
As always, feedback is appreciated.
Best regards,
Florian Riedl
rsyslog 6.4.0 (v6-stable)
Download file name: rsyslog 6.4.0 (stable)
rsyslog 6.4.0 (stable)
md5sum: d81f74b09829a38ac91cf85a08c5ab19
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 6.4.0 File size: 2.530 MB
How to check if config variables are used?
Sometimes you might wonder, if the configuration you created is really used. At least parts of it. This could really happen in a lot of situations. Currently, the config format is changed a lot. This forces users who want to use the new format to use a mixed mode of old and new config style. And this is where a lot of confusion can occur, which results in not properly set config variables. In fact, you just need to create some consistency in the configuration. Most output modules are already updated. If you want to use the new format, you cannot use some old config directives and use some new config directives at the same time. The old ones will be simply ignored then. Instead the default values will be used. A very common case is with queues and this is what I will use for my example. I will show, how you can identify if configuration directives are used correctly. We will use the debug log for this. The rsyslog version I will use is the 6.3.12 beta. In this version, the main message queue still needs to be configured with the old config directives, whereas action queues already support the new config directives. You can enable debug mode for rsyslog with the following commands in a terminal:
export RSYSLOG_DEBUGLOG="/path/to/debuglog" export RSYSLOG_DEBUG="Debug"
You can now start rsyslog on the same command line with:
rsyslogd -c6
You will usually see the debug output in that same terminal, as rsyslog runs in the foreground. That should now just serve as a indicator, that the debug output works. Now here is the config snippet I used:
$ActionQueueType LinkedList $ActionQueueSize 2000000 $ActionQueueTimeoutEnqueue 0 $ActionQueueDequeueBatchSize 400 *.* action(type="omfwd" target="10.10.10.12" port="514" protocol="udp")
As you can see, we configured the action queue with some custom variables in the old fashion, basically the action queue and the action itself with the new style. If you create a new debug file now and review it, search for “action 1” in this case. You should see the following.
rsyslog 6.3.11 (v6-beta) released
This is a new beta release for the v6 branch. It only contains bugfixes. For more details, please take a look into the ChangeLog.
ChangeLog:
http://www.rsyslog.com/changelog-for-6-3-11-v6-beta/
Download:
http://www.rsyslog.com/rsyslog-6-3-11-beta/
As always, feedback is appreciated.
Best regards,
Florian Riedl