syslog-ng 3.3.4 has been released
------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 3.3.4 SUMMARY : new stable release DATE : Jan 19, 2012 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Open Source Edition (3.3.4) has been released. For latest fixes in the 3.3.x feature branch you are recommended to upgrade to this version. CHANGES: 3.3.4 Mon, 16 Jan 2012 23:07:46 +0100 Highlights ========== This release is aimed fixing bugs in the 3.3.x series, with one more important change: there's an incompatible change in the processing of <action> tags in the db-parser() database format (aka patterndb), see below for more details. Bugfixes: ========= * Fixed set() and subst() rewrite operations to work properly on the value() parameter specified in the configuration even if they are referenced at multiple spots in the configuration file. Earlier the 2nd and subsequent invocation of the rewrite rule changed $MESSAGE. * Fixed csv-parser() to work even if it is invoked at multiple spots in the configuration file. Earlier, the 2nd and subsequent references of the parser rule forgot the list of column names and the input template. * Fixed the processing of condition() parameter in rewrite rules, which was broken if it contained a filter() function call. * Fixed program() destination to properly kill the child process on reload and shutdown. * Fixed a potential division by zero error which could happen for large data rates due to a race in an unlocked region. * Fixed an assertion failure in mongodb destination that happened due to a race condition at high data rates. * Fixed an fd leak in the control socket code, that caused the control connection file descriptors to be leaked. Other changes ============= * db-parser() automatically sets a tag named '.classifier.unknown' if the message doesn't match. * The use of actions in db-parser() for messages without a correllation context was inconsistently indexing messages. For actions in rules that had correllation @0 was the new message being generated, and @1 was the message that triggered the rule. Without correllation @0 was used for the triggering message, which is greatly inconsistent and unintuitive. This was fixed by changing the behaviour for rules without correllation, now both correllation and non-correllation rules use @0 for the new message, and @1 for the triggering message. This is an incompatible change in the db-parser() format. * The value of the $TAGS macro is added to pdbtool match output. * unix-dgram() and unix-stream() error logging on systemd failures became more detailed for easier troubleshooting. Credits: ======== syslog-ng is developed as a community project, and as such it relies on volunteers to do the work necessarily to produce syslog-ng. Reporting bugs, testing changes, writing code or simply providing feedback are all important contributions, so please if you are a user of syslog-ng, contribute. These people have helped in this release: Attila M. Magyar (BalaBit) Balazs Scheidler (BalaBit) Costa Farber Dmitry Gilev Evan Rempel (University of Victoria) Fried Zoltan (BalaBit) Gergely Nagy (BalaBit) Jakub Jankowski (SuperHost.pl) John Morrissey (Horde.net) Michael Hocke (New York University) Michal Schmidt (RedHat) Peter Eisenlohr (Inform Software) Svante Signell (Telia.se) Thomas Wollner DOWNLOAD: You can download the source or binary packages from: http://www.balabit.com/network-security/syslog-ng/opensource-logging-system/... The documentation of the syslog-ng Open Source Edition is available in The syslog-ng Open Source Edition Administrator's Guide at http://www.balabit.com/support/documentation/
On 19/01/2012 18:51, devel@balabit.hu wrote:
------------------------------------------------------------------------------
PACKAGE : syslog-ng VERSION : 3.3.4 SUMMARY : new stable release DATE : Jan 19, 2012 ------------------------------------------------------------------------------
DESCRIPTION:
A new stable version of syslog-ng Open Source Edition (3.3.4) has been released. For latest fixes in the 3.3.x feature branch you are recommended to upgrade to this version.
I updated my local git tree and I don't see a tag for 3.3.4? $ git tag v2.1.1 v2.1alpha1 v2.1beta1 v2.1beta2 v3.0.1 v3.0.2 v3.1.0 v3.1beta1 v3.1beta2 v3.2alpha1 v3.2beta1 v3.3.0alpha1 v3.3.0alpha2 v3.3.0beta2 v3.3.1 v3.3.2 It would be really useful if you could tag it or post the commit ref that 3.3.4 relates to? I did a "git pull" which, afaik, pulls the tags too. Thanks.
CHANGES:
3.3.4 Mon, 16 Jan 2012 23:07:46 +0100
Highlights ========== This release is aimed fixing bugs in the 3.3.x series, with one more important change: there's an incompatible change in the processing of <action> tags in the db-parser() database format (aka patterndb), see below for more details.
Bugfixes: =========
* Fixed set() and subst() rewrite operations to work properly on the value() parameter specified in the configuration even if they are referenced at multiple spots in the configuration file. Earlier the 2nd and subsequent invocation of the rewrite rule changed $MESSAGE.
* Fixed csv-parser() to work even if it is invoked at multiple spots in the configuration file. Earlier, the 2nd and subsequent references of the parser rule forgot the list of column names and the input template.
* Fixed the processing of condition() parameter in rewrite rules, which was broken if it contained a filter() function call.
* Fixed program() destination to properly kill the child process on reload and shutdown.
* Fixed a potential division by zero error which could happen for large data rates due to a race in an unlocked region.
* Fixed an assertion failure in mongodb destination that happened due to a race condition at high data rates.
* Fixed an fd leak in the control socket code, that caused the control connection file descriptors to be leaked.
Other changes ============= * db-parser() automatically sets a tag named '.classifier.unknown' if the message doesn't match.
* The use of actions in db-parser() for messages without a correllation context was inconsistently indexing messages. For actions in rules that had correllation @0 was the new message being generated, and @1 was the message that triggered the rule. Without correllation @0 was used for the triggering message, which is greatly inconsistent and unintuitive. This was fixed by changing the behaviour for rules without correllation, now both correllation and non-correllation rules use @0 for the new message, and @1 for the triggering message. This is an incompatible change in the db-parser() format.
* The value of the $TAGS macro is added to pdbtool match output.
* unix-dgram() and unix-stream() error logging on systemd failures became more detailed for easier troubleshooting.
Credits: ======== syslog-ng is developed as a community project, and as such it relies on volunteers to do the work necessarily to produce syslog-ng.
Reporting bugs, testing changes, writing code or simply providing feedback are all important contributions, so please if you are a user of syslog-ng, contribute.
These people have helped in this release:
Attila M. Magyar (BalaBit) Balazs Scheidler (BalaBit) Costa Farber Dmitry Gilev Evan Rempel (University of Victoria) Fried Zoltan (BalaBit) Gergely Nagy (BalaBit) Jakub Jankowski (SuperHost.pl) John Morrissey (Horde.net) Michael Hocke (New York University) Michal Schmidt (RedHat) Peter Eisenlohr (Inform Software) Svante Signell (Telia.se) Thomas Wollner
DOWNLOAD:
You can download the source or binary packages from:
http://www.balabit.com/network-security/syslog-ng/opensource-logging-system/...
The documentation of the syslog-ng Open Source Edition is available in The syslog-ng Open Source Edition Administrator's Guide at
http://www.balabit.com/support/documentation/
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
On Fri, 2012-01-20 at 10:25 +0000, Dave Haywood wrote:
On 19/01/2012 18:51, devel@balabit.hu wrote:
------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 3.3.4 SUMMARY : new stable release DATE : Jan 19, 2012 ------------------------------------------------------------------------------
DESCRIPTION:
A new stable version of syslog-ng Open Source Edition (3.3.4) has been released. For latest fixes in the 3.3.x feature branch you are recommended to upgrade to this version.
I updated my local git tree and I don't see a tag for 3.3.4?
$ git tag v2.1.1 v2.1alpha1 v2.1beta1 v2.1beta2 v3.0.1 v3.0.2 v3.1.0 v3.1beta1 v3.1beta2 v3.2alpha1 v3.2beta1 v3.3.0alpha1 v3.3.0alpha2 v3.3.0beta2 v3.3.1 v3.3.2
It would be really useful if you could tag it or post the commit ref that 3.3.4 relates to? I did a "git pull" which, afaik, pulls the tags too.
Did that, thanks. Seems my VPN connection wasn't alive when I did the release, thus it didn't get pushed. But I've now pushed all tags to both git.balabit.hu and github.com
On 22/01/2012 12:35, BalaBit Development Team wrote:
On Fri, 2012-01-20 at 10:25 +0000, Dave Haywood wrote:
On 19/01/2012 18:51, devel@balabit.hu wrote:
------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 3.3.4 SUMMARY : new stable release DATE : Jan 19, 2012 ------------------------------------------------------------------------------
DESCRIPTION:
A new stable version of syslog-ng Open Source Edition (3.3.4) has been released. For latest fixes in the 3.3.x feature branch you are recommended to upgrade to this version. I updated my local git tree and I don't see a tag for 3.3.4?
$ git tag v2.1.1 v2.1alpha1 v2.1beta1 v2.1beta2 v3.0.1 v3.0.2 v3.1.0 v3.1beta1 v3.1beta2 v3.2alpha1 v3.2beta1 v3.3.0alpha1 v3.3.0alpha2 v3.3.0beta2 v3.3.1 v3.3.2
It would be really useful if you could tag it or post the commit ref that 3.3.4 relates to? I did a "git pull" which, afaik, pulls the tags too.
Did that, thanks. Seems my VPN connection wasn't alive when I did the release, thus it didn't get pushed. But I've now pushed all tags to both git.balabit.hu and github.com
Hmm, still not seeing a 3.3.4 tag! ~/syslog-ng-3.3$ git pull remote: Generating pack... remote: Done counting 1 objects. remote: Deltifying 1 objects... remote: 100% (1/1) done remote: Total 1 (delta 0), reused 0 (delta 0) Unpacking objects: 100% (1/1), done. From git://git.balabit.hu/bazsi/syslog-ng-3.3 * [new tag] v3.3.3 -> v3.3.3 Already up-to-date. ~/syslog-ng-3.3$ git tag v2.1.1 v2.1alpha1 v2.1beta1 v2.1beta2 v3.0.1 v3.0.2 v3.1.0 v3.1beta1 v3.1beta2 v3.2alpha1 v3.2beta1 v3.3.0alpha1 v3.3.0alpha2 v3.3.0beta2 v3.3.1 v3.3.2 v3.3.3 ~/syslog-ng-3.3$ git rev-parse HEAD 3dc36259904aa1b206ee52e6ac2cd1266957cef0 And on the 3.4 repo: ~/syslog-ng-3.4$ git pull Already up-to-date. ~/syslog-ng-3.4$ git tag v2.1.1 v2.1alpha1 v2.1beta1 v2.1beta2 v3.0.1 v3.0.2 v3.1.0 v3.1beta1 v3.1beta2 v3.2alpha1 v3.2beta1 v3.3.0alpha1 v3.3.0alpha2 ~/syslog-ng-3.4$ git rev-parse HEAD ece855da52124744fb14858c54906b6e901f58b2 :s Regards, Dave.
Dave Haywood <tla@oak.selfip.net> writes:
Did that, thanks. Seems my VPN connection wasn't alive when I did the release, thus it didn't get pushed. But I've now pushed all tags to both git.balabit.hu and github.com
Hmm, still not seeing a 3.3.4 tag!
Interesting... I just did a fresh clone of git://git.balabit.hu/bazsi/syslog-ng-3.3, and I do see a v3.3.4 tag. Although, it seems that it's on a commit that's not on master. -- |8]
Gergely Nagy <algernon@balabit.hu> writes:
Dave Haywood <tla@oak.selfip.net> writes:
Did that, thanks. Seems my VPN connection wasn't alive when I did the release, thus it didn't get pushed. But I've now pushed all tags to both git.balabit.hu and github.com
Hmm, still not seeing a 3.3.4 tag!
Interesting... I just did a fresh clone of git://git.balabit.hu/bazsi/syslog-ng-3.3, and I do see a v3.3.4 tag.
Although, it seems that it's on a commit that's not on master.
Further research revealed that while the tag is present on both github and git.balabit.hu, the master on the latter is three commits behind github. Since Bazsi pushes to github more often (and more reliably), I'd suggest to change your remote to github. git remote set-url origin git://github.com/bazsi/syslog-ng-3.3.git should do the trick. -- |8]
Has anyone tried to build an RPM using the supplied .spec file? This works when building on a host where syslog-ng 3.3.4 is already installed, but if you try to do this on a host where a previous version of syslog-ng is installed (such as 3.3.3) the rpmbuild process compiles everything correctly, and links against libsyslog-ng but then the rpmbuild script to a relink using libtool and -rpath which "finds" libsyslog-ng in the install directory rather than the build tree, and ends up linking agains the currently installed libsyslog-ng which in my case is 3.3.3 % rpm -qpR /my/build/tree/syslog-ng-3.3.4-1.x86_64.rpm ... libsyslog-ng-3.3.3.so()(64bit) libsyslog-ng-3.3.4.so()(64bit) libsyslog-ng-crypto.so()(64bit) Then at RPM upgrade time, the dependency check fails since libsyslog-ng-3.3.3.so will no longer be available when 3.3.3 is replaced by 3.3.4 Can this be fixed in syslog-ng/Makefile syslog_ng_LDADD = ... -lsyslog-ng and change it to syslog_ng_LDADD = ...-lsyslog-ng-3.3.4 Can anyone shed some light on this for me. Evan.
participants (5)
-
BalaBit Development Team
-
Dave Haywood
-
devel＠balabit.hu
-
Evan Rempel
-
Gergely Nagy