rsyslog

The rocket-fast system for log processing

rsyslog 7.3.9 (v7-devel) released

By adisconteamPosted on Posted in News, Release AnnouncementTagged , , , , , , ,

We have just released v 7.3.9 of the rsyslog development branch. The most important feature of this release is the capability to digitally sign log files. This is done via RFC3161. It also contains some other feature enhancements as well as bug fixes. Note that 7.3.9 is almost feature-complete and can be considered a beta. It is our goal to release a new v7.4 stable within the next few weeks.

ChangeLog:

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

Download:

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

As always, feedback is appreciated.

Best regards,
Tim Eifler

Changelog for 7.3.9 (v7-devel)

By adisconteamPosted on Posted in ChangelogTagged , , , , , , , ,

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

By adisconteamPosted on Posted in News, Release AnnouncementTagged , , , , , , , ,

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

By Adiscon SupportPosted on Posted in News, Release AnnouncementTagged , , , , , , , , , ,

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)

By Adiscon SupportPosted on Posted in ChangelogTagged , , , , , , , ,

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
Scroll to top