Changelog for 7.6.2 (v7-stable)
Version 7.6.2 [v7.6-stable] 2014-03-17
- support for librelp 1.2.4
This was necessary due to the problems with librelp 1.2.3 API stability.
We now use the new native 1.2.4 APIs to learn about the state of librelp’s TLS support.
For obvious reasons, librelp 1.2.4 is now required.
rsyslog 7.6.1 (v7-stable) released
This releases is a recommended update for all users of the 7.6 branch.
ChangeLog:
http://www.rsyslog.com/changelog-for-7-6-1-v7-stable/
Download:
http://www.rsyslog.com/rsyslog-7-6-1-v7-stable/
As always, feedback is appreciated.
Best regards,
Florian Riedl
rsyslog 7.6.1 (v7-stable)
Download file name: rsyslog 7.6.1 (stable)
rsyslog 7.6.1 (stable)
sha256 hash: 357f089d866c351d5fe5b7139fa85b
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 7.6.1 File size: 3.05 MB
Changelog for 7.6.1 (v7-stable)
Version 7.6.1 [v7.6-stable] 2014-03-13
- added “action.reportSuspension” action parameter This now permits to control handling on a per-action basis rather to the previous “global setting only”.
- “action resumed” message now also specifies module type which makes troubleshooting a bit easier. Note that we cannot output all the config details (like destination etc) as this would require much more elaborate code changes, which we at least do not like to do in the stable version.
- better and more consistent action naming, action queues now always contain the word “queue” after the action name – add support for “tls-less” librelp we now require librelp 1.2.3, as we need the new error code definition See also: https://github.com/rsyslog/
librelp/issues/1 - build system improvements
- autoconf subdir option
- support for newer json-c packages Thanks to Michael Biebl for the patches.
- imjournal enhancements:
- log entries with empty message field are no longer ignored
- invalid facility and severity values are replaced by defaults
- new config parameters to set default facility and severity Thanks to Tomas Heinrich for implementing this
- bugfix: ompipe did resume itself even when it was still in error See: https://github.com/rsyslog/
rsyslog/issues/35 Thanks to github user schplat for reporting - bugfix: “action xxx suspended” did report incorrect error code
- bugfix: ommongodb’s template parameter was mandatory but should have been optional Thanks to Alain for the analysis and the patch.
- bugfix: only partial doc was put into distribution tarball Thanks to Michael Biebl for alerting us. see also: https://github.com/rsyslog/
rsyslog/issues/31 - bugfix: async ruleset did process already-deleted messages Thanks to John Novotny for the patch.
rsyslog 7.6.0 (v7-stable) released
This is the first release of rsyslog 7.6 in the v7-stable branch. Since 7.4 a lot of new functions have found their way into rsyslog. With 7.6 being the successor of the 7.5 development branch, everything that has been added there has now found its way into the stable version. The major additions consist of
- imrelp/omrelp now support TLS & (zip) compression
- impstats is now emitting resource usage counters, can directly emit delta values and can now be bound to a ruleset
- mmpstrucdata is a new module to parse RFC5424 structured data into JSON message properties
- mmutf8fix is a new module to fix invalid UTF-8 sequences
- mmsequence is a new module that helps with action load balancing
- new defaults for main/ruleset queues to be more enterprise-like
Also the new stable version has undergone a lot of bug fixes, performance improvements and optimizations that make rsyslog 7.6 a lot more reliable and performing than before. Also, requirements have changed a little. For rsyslog 7.6 you now require librelp 1.1.4 and libestr 0.1.7 due to major fixes.
More detailed information is available in the ChangeLog.
ChangeLog: http://www.rsyslog.com/changelog-for-7-6-0-v7-stable/
Download: http://www.rsyslog.com/rsyslog-7-6-0-v7-stable/
As always, feedback is appreciated.
Best regards,
Florian Riedl
rsyslog 7.6.0 (v7-stable)
Download file name: rsyslog 7.6.0 (stable)
rsyslog 7.6.0 (stable)
sha256 hash: c40da756369dbb560b26f5baab5bdb
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 7.6.0 File size: 2.60 MB
Changelog for 7.6.0 (v7-stable)
Version 7.6.0 [v7.6-stable] 2014-01-??
This starts a new stable branch based on 7.5.8 plus the following changes:
- bugfix: imuxsock input parameters were not accepted due to copy&paste error.
Thanks to Andy Goldstein for the fix. - added ProcessInternalMessages global system parameter
This permits to inject rsyslog status messages into *another* main syslogd or the journal. - new dependency: liblogging-stdlog (for submitting to external logger)
- bugfix: json templates are improperly created
Strings miss the terminating NUL character, which obviously can lead to all sorts of problems.
See also: https://github.com/rsyslog/rsyslog/issues/27
Thanks to Alain for the analysis and the patch. - ompgsql bugfix: improper handling of auto-backgrounding mode
If rsyslog was set to auto-background itself (default code behaviour, but many distros now turn it off for good reason), ompgsql could not properly connect. This could even lead to a segfault. The core reason was that a PG session handle was kept open over a fork, something that is explicitely forbidden in the PG API.
Thanks to Alain for the analysis and the patch.
rsyslog 7.4.10 (v7-stable) released
We have just released 7.4.10 of the v7-stable branch. This is the final bug-fixing release for rsyslog 7.4. The new version will be 7.6. More detailed information is available in the ChangeLog.
ChangeLog:
Download: http://www.rsyslog.com/rsyslog-7-4-10-v7-stable/
As always, feedback is appreciated.
Best regards,
Florian Riedl
rsyslog 7.4.10 (v7-stable)
Download file name: rsyslog 7.4.10 (stable)
rsyslog 7.4.10 (stable)
sha256 hash: ab1d26da2bfd38db34dd991a9c5d93
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 7.4.10 File size: 2.92 MB
Changelog for 7.4.10 (v7-stable)
Version 7.4.10 [v7.4-stable] 2014-02-12
- bugfix: json templates are improperly created
Strings miss the terminating NUL character, which obviously can lead to all sorts of problems.
See also: https://github.com/rsyslog/rsyslog/issues/27
Thanks to Alain for the analysis and the patch. - ompgsql bugfix: improper handling of auto-backgrounding mode
If rsyslog was set to auto-background itself (default code behaviour, but many distros now turn it off for good reason), ompgsql could not properly connect. This could even lead to a segfault. The core reason was that a PG session handle was kept open over a fork, something that is explicitely forbidden in the PG API.
Thanks to Alain for the analysis and the patch.