bugfix

Changelog for 7.3.9 (v7-devel)

Version 7.3.9 [devel] 2013-03-27

  • support for signing logs added
  • imudp: now supports user-selectable inputname
  • omlibdbi: now supports transaction interface
    if recent enough lbdbi is present
  • imuxsock: add ability to NOT create/delete sockets during startup and
    shutdown
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=259
  • imfile: errors persisting state file are now reported
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=292
  • imfile: now detects file change when rsyslog was inactive
    Previosly, this case could not be detected, so if a file was overwritten
    or rotated away while rsyslog was stopped, some data was missing. This
    is now detected and the new file being forwarded right from the
    beginning.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=228
  • updated systemd files to match current systemd source
  • bugfix: imudp scheduling parameters did affect main thread, not imudp
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=409
  • bugfix: build problem on platforms without GLOB_NOMAGIC
  • bugfix: build problems on non-Linux platforms
  • bugfix: stdout/stderr were not closed on forking
    but were closed when running in the forground – this was just reversed
    of what it should be. This is a regression of a recent change.

rsyslog 7.3.8 (v7-devel) released

We have just released v 7.3.8 of the rsyslog development branch. The new version supports specifying IPv4/v6 only fo imrelp. Other than that, it is a bug-fixing release.

ChangeLog:

http://www.rsyslog.com/changelog-for-7-3-8-v7-devel/

Download:

http://www.rsyslog.com/rsyslog-7-3-7-v8-devel/

As always, feedback is appreciated.

Best regards,
Tim Eifler

rsyslog 7.3.7 (v7-devel) released

We have just released v 7.3.7 of the rsyslog development branch. This release offers some important new features, most importantly a plugin to anonymize IPv4 addresses and a plugin to write to the systemd journal. Also, the field() RainerScript function has been upgraded to support multi-character field delimiters. There is also a number of bug fixes present.

ChangeLog:

http://www.rsyslog.com/changelog-for-7-3-7-v7-devel/

Download:

http://www.rsyslog.com/rsyslog-7-3-7-v7-devel/

As always, feedback is appreciated.

Best regards,
Florian Riedl

Changelog for 7.3.7 (v7-devel)

Version 7.3.7  [devel] 2013-03-12

  • add support for anonymizing IPv4 addresses
  • add support for writing to the Linux Journal (omjournal)
  • imuxsock: add capability to ignore messages from ourselves
    This helps prevent message routing loops, and is vital to have if omjournal is used together with traditional syslog.
  • field() function now supports a string as field delimiter
  • added ability to configure debug system via rsyslog.conf
  • bugfix: imuxsock segfault when system log socket was used
  • bugfix: mmjsonparse segfault if new-style config was used
  • bugfix: script == comparison did not work properly on JSON objects
  • bugfix: field() function did never return “***FIELD NOT FOUND***”
    instead it returned “***ERROR in field() FUNCTION***” in that case

Changelog for 7.2.6 (v7-stable)

Version 7.2.6  [v7-stable] 2013-03-05

  • slightly improved config parser error messages when invalid escapes happen
  • bugfix: include files got included in the wrong order
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=411
    This happens if an $IncludeConfig directive was done on multiple files (e.g. the distro default of $IncludeConfig /etc/rsyslog.d/*.conf). In that case, the order of include file processing is reversed, which could lead to all sorts of problems.
    Thanks to Nathan Stratton Treadway for his great analysis of the problem, which made bug fixing really easy.
  • bugfix: omelasticsearch failed when authentication data was provided … at least in most cases it emitted an error message:
    “snprintf failed when trying to build auth string”
    Thanks to Joerg Heinemann for alerting us.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=404
  • bugfix: some property-based filter were incorrectly parsed
    This usually lead to a syntax error on startup and rsyslogd not actually starting up. The problem was the regex, which did not care for double quote characters to follow in the action part – unfortunately something that can frequently happen with v6+ format. An example:
    :programname, isequal, “as” {action(type=”omfile” …) }
    Here, the part
    :programname, isequal, “as” {action(type=”omfile”
    was treated as the property filter, and the rest as action part. Obviously, this did not work out. Unfortunately, such situations usually resulted in very hard to understand error messages.
Scroll to top