rsyslog

The rocket-fast system for log processing

bugfix

Changelog for 7.6.3 (v7-stable)

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

Version 7.6.3 [v7.6-stable] 2014-03-27

  • add capability to override GnuTLS path in build process
    Thanks to Clayton Shotwell for the patch
  • support for librelp 1.2.5
    Support new return states of librelp 1.2.5 to emit better error messages. For obvious reasons, librelp 1.2.5 is now required.
  • bugfix: ompipe used invalid default template
    This is a regression from an old change (didn’t track it down precisely, but over a year ago). It used the Forwarding template instead of the file template (so we have a full syslog header). This fix corrects it back to previous behaviour, but new scripts that used the wrong format may now need to have the RSYSLOG_ForwardingFormat template explicitely be applied.
    closes: https://github.com/rsyslog/rsyslog/issues/50
  • bugfix: ompipe did emit many suspension messages for /dev/xconsole
    (hopefully now) closes: https://github.com/rsyslog/rsyslog/issues/35
    When it was present, but nobody reading from it. The problem is the way the rsyslog v7 engine tries to resolve failures in outputs. It does some retries, and along those lines some state information gets lost and it is close to impossible to retain it. However, the actual root problem is that ompipe does not reliably detect if it is able to recover. The problem here is that it actually does not know this before it does an actual write. These two things together mess up the logic that suppresses invalid resumption/suspension messages (actually, the plugin switches state really that often). Nevertheless, the prime problem with /dev/xconsole (and probably most other pipes as well) is that it gets full. So I have now added code that checks, during resume processing, if the pipe is writable. If it is not, resume is deferred. That should address the case.

rsyslog 7.6.1 (v7-stable) released

By Adiscon SupportPosted on Posted in News, Release AnnouncementTagged , , , , ,
This version is the first bug-fixing release for 7.6. In addition to bugfixes, it also offers some new, unintrusive, features. Most importantly, the way action suspension and resumption messages can now be configured on a finger grain basis. The action naming has been improved and kept consistent and imjournal can now better handle invalid entries in systemd journal.

This releases is a recommended update for all users of the 7.6 branch.

Note that now librelp 1.2.3 is required as we process it’s new error codes emitted when librelp does not support TLS.

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

Changelog for 7.6.1 (v7-stable)

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

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.

Changelog for 7.6.0 (v7-stable)

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

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.

Changelog for 7.4.10 (v7-stable)

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

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.

rsyslog 8.1.5 (v8-devel) released

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

We have just released 8.1.5 of the v8-devel branch. This release offers some important bug fixes and an enhanced imfile. It now supports inotify and has no longer a fixed limit on the number of files that can be monitored. Note that inotify must be enabled. By default, the previous polling mode is used. For details see parameter “mode” in the doc: http://www.rsyslog.com/doc/imfile.html
ChangeLog: http://www.rsyslog.com/changelog-for-8-1-5-v8-devel/
Download: http://www.rsyslog.com/rsyslog-8-1-5-v8-devel/

Feedback is *very much* appreciated.

Best regards, Florian Riedl

Changelog for 8.1.5 (v8-devel)

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

Version 8.1.5 [devel] 2014-01-24

  • imfile now supports inotify (but must be explicitely turned on)
  • imfile no longer has a limit on number of monitored files
  • 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: imuxsock input parameters were not accepted due to copy&paste error. Thanks to Andy Goldstein for the fix.

rsyslog 7.4.9 (v7-stable) released

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

We have just released 7.4.9 of the v7-stable branch.

While we initially did not intend to do another v7.4 release, we got some important fixes which we wanted to be available for 7.4, so we decided to do one more release. Note that also a new feature is included. The “processInternalMessages” global parameter now permits to tell rsyslog to send it’s own error messages to another system logger. This is most beneficial for systemd-based systems, where this permits rsyslog messages to show up in the service status command (but note that this requires configuration).

More detailed information is available in the ChangeLog.

ChangeLog:

http://www.rsyslog.com/changelog-for-7-4-9-v7-stable/

Download:

http://www.rsyslog.com/rsyslog-7-4-9-v7-stable/

As always, feedback is appreciated.

Best regards,
Florian Riedl

Changelog for 7.4.9 (v7-stable)

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

Version 7.4.9  [v7.4-stable] 2014-01-22

  • added ProcessInternalMessages global system parameter
    This permits to inject rsyslog status messages into *another* main syslogd or the journal.
  • bugfix: imuxsock input parameters were not accepted due to copy&paste error. Thanks to Andy Goldstein for the fix.
  • bugfix: potential double-free in RainerScript equal comparison happens if the left-hand operand is JSON object and the right-hand operand is a non-string that does not convert to a number (for example, it can be another JSON object, probably the only case that could happen in practice). This is very unlikely to be triggered.
  • bugfix: some RainerScript Json(Variable)/string comparisons were wrong
Scroll to top