imfile

Changelog for 7.6.4 (v7-stable)

Version 7.6.4 [v7.6-stable] 2014-09-12

  • add –enable-generate-man-pages configure switch (default: enabled)
    This forces generation of man pages, even if cached ones exists. This “fixes” a typical release tarball nit. While it is hackish, the benefit is clear given the history of failed tarball releases since we changed the cached man page handling. It was just too easy to get that wrong.
  • removed obsolete –disable-fsstnd configure option
    Thanks to Thomas D. for alerting us.
    Closes: https://github.com/rsyslog/rsyslog/issues/72
  • permits to build against json-c 0.12
    Unfortunately, json-c had an ABI breakage, so this is necessary. Note that versions prior to 0.12 had security issues (CVE-2013-6370, CVE-2013-6371) and so it is desirable to link against the new version.
    Thanks to Thomas D. for the patch. Note that at least some distros have fixed the security issue in older versions of json-c, so this seems to apply mostly when building from sources.
  • new omfile default module parameters
    • filecreatemode
    • fileowner
    • fileownernum
    • filegroup
    • filegroupnum
    • dirowner
    • dirownernum
    • dirgroup
    • dirgroupnum

    Thanks to Karol Jurak for the patch.

  • bugfix: memory leak in TCP TLS mode
  • bugfix: imfile: if a state file for a different file name was set, that different file (name) was monitored instead of the configured one. Now, the state file is deleted and the correct file monitored.
    closes: https://github.com/rsyslog/rsyslog/issues/103
  • bugfix: using UUID property could cause segfault
  • bugfix: mmutf8fix did not detect two invalid sequences
    Thanks to Axel Rau for the patch.
  • bugfix: file descriptor leak with Guardtime signatures
    When a .gtstate file is opened it is never closed. This is especially bad when dynafiles frequently get evicted from dynafile cache and be re-opened again.
  • bugfix: busy loop in tcp listener when running out of file descriptors
    Thanks to Susant Sahani for the patch.
  • bugfix: mishandling of input modules not supporting new input instances
    If they did not support this, accidently the output module part of the module union was written, leading to unpredictable results. Note: all core modules do support this interface, but some contributed or very old ones do not.
  • bugfix: double-free when ruleset() parser parameters were used
    While unlikely, this could cause stability issues even after the config phase.
  • bugfix: output modules with parameters with multiple passing modes could caused strange behaviour including aborts
    This was due to the fact that the action module only preserved and processed the last set passing mode. Note that this was not a problem for the plugins provided by the rsyslog git: none of them uses different passing modes.
    Thanks to Tomas Heinrich for providing a very detailled bug report.
  • various fixes after coverty scan
    These do not address issues seen in practice but those seen by the tool. Some of them may affect practical deployments.
    Thanks to Tomas Heinrich for the patches.
  • bugfix imuxsock: “Last message repeated…” was not emitted at shutdown
    The “Last message repeated…” notice didn’t get printed if rsyslog was shut down before the repetition was broken.
    Thanks to Tomas Heinrich for the patch.
  • bugfix: make dist failed when GUARDTIME or LIBGCRYPT feature was disabled
  • bugfix: mmjsonparse did not build with json-c < 0.10
    This was a regression introduced some time in the past in order to support API changes in json-c. Now we check for the version and use proper code.
  • bugfix: mmanon did not properly anonymize IP addresses starting with ‘9’
    Thanks to defa-at-so36.net for reporting this problem.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=529

rsyslog 8.1.5 (v8-devel) released

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)

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.5.5 (v7-devel) released

This release offers some important bug fixes and exciting new features. Most importantly, imudp can now use multiple input threads for even higher UDP input throughput. And imfile now longer has a hardcoded limit on the number of files that can be monitored. You can now monitor as many files as you like. Support for setting default timezones has been added to imptcp and imudp, but is still in experimental state (but feel free to use it if it suits you!). More detailed information is available in the changelog.

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

Download: http://www.rsyslog.com/rsyslog-7-5-5-v7-devel/

As always, feedback is appreciated.

Best regards, Florian Riedl

Changelog for 7.5.5 (v7-devel)

Version 7.5.5 [devel] 2013-10-16

  • imfile: permit to monitor an unlimited number of files
  • imptcp: add “defaultTZ” input parameter
  • imudp: support for multiple receiver threads added
  • imudp: add “dfltTZ” input config parameter
  • bugfix: memory leak in mmnormalize
  • bugfix: mmutf8fix did not properly handle invalid UTF-8 at END of message if the very last character sequence was too long, this was not detected
    Thanks to Risto Vaarandi for reporting this problem.
  • mmanon: removed the check for specific “terminator characters” after  last octet. As it turned out, this didn’t work in practice as there was an enormous set of potential terminator chars — so removing them was the best thing to do. Note that this may change behaviour of existing installations. Yet, we still consider this an important bugfix, that should be applied to the stable branch.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=477
    Thanks to Muri Cicanor for initiating the discussion
  • now requires libestr 0.1.7 as early versions had a nasty bug in string comparisons
  • bugfix: mmanon did not detect all IP addresses in rewrite mode
    The problem occured if two IPs were close to each other and the first one was shrunk.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=485
    Thanks to micah-at-riseup.net for reporting this bug
  • bugfix: mmanon sometimes used invalid replacement char in simple mode depending on configuration sequence, the replacement character was set to ‘s’ instead of the correct value. Most importantly, it was set to ‘s’ if simple mode was selected and no replacement char set.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=484
    Thanks to micah-at-riseup.net for reporting this bug
  • bugfix: memory leak in mmnormalize
  • bugfix: array-based ==/!= comparisions lead to invalid results
    This was a regression introduced in 7.3.5 bei the PRI optimizer

rsyslog 7.5.3 (v7-devel) released

This release offers important new features like support for global and local variables, improvements in imfile multi-line handling and enhancements in the statistics subsystem. It also include bug fixes, including those imported from 7.4.4.

Note that the new imfile multi-line handling may cause a change of behaviour if you use it together with the input() config statement. For details, please see

http://blog.gerhards.net/2013/09/imfile-multi-line-messages.html

Users of the rsyslog development branch are strongly encouraged to upgrade to the new version.

ChangeLog:

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

Download:

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

As always, feedback is appreciated.

Best regards,
Florian Riedl

Changelog for 7.5.3 (v7-devel)

Version 7.5.3 [devel] 2013-09-11

  • imfile: support for escaping LF characters added embedded LF in syslog messages cause a lot of trouble. imfile now has the capability to escape them to “#012″ (just like the regular control character escape option). This requires new-style input statements to be used. If legacy configuration statements are used, LF escaping is always turned off to preserve compatibility.
    NOTE: if input() statements were already used, there is a CHANGE OF BEHAVIOUR: starting with this version, escaping is enabled by default. So if you do not want it, you need to add escapeLF=”off” to the input statement. Given the trouble LFs cause and the fact that the majority of installations still use legacy config, we considered this behaviour change acceptable and useful.
    see also: http://blog.gerhards.net/2013/09/imfile-multi-line-messages.html
  • add support for global and local variables
  • bugfix: queue file size was not correctly processed
    this could lead to using one queue file per message for sizes >2GiB
    Thanks to Tomas Heinrich for the patch.
  • add main_queue() configuration object to configure main message queue
  • bugfix: stream compression in imptcp caused timestamp to be corrupted
  • imudp: add ability to specify SO_RCVBUF size (rcvbufSize parameter)
  • imudp: use inputname for statistics, if configured
  • impstats: add process resource usage counters [via getrusage()]
  • impstats: add paramter “resetCounters” to report delta values possible for most, but not all, counters. See doc for details.
  • librelp 1.2.0 is now required
  • make use of new librelp generic error reporting facility
    This leads to more error messages being passed to the user and thus simplified troubleshooting.
  • bugfix: very small memory leak in imrelp
    more or less cosmetic, a single memory block was not freed, but this only happens immediately before termination (when the OS automatically frees all memory). Still an annoyance e.g. in valgrind.
  • fix compile problem in debug build
  • imported fixes from 7.4.4

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.

Changelog for 7.2.2 (v7-stable)

Version 7.2.2 [v7-stable] 2012-10-16

  • doc improvements
  • enabled to build without libuuid, at loss of uuid functionality
    this enables smoother builds on older systems that do not support
    libuuid. Loss of functionality should usually not matter too much as
    uuid support has only recently been added and is very seldom used.
  • bugfix: omfwd did not properly support “template” parameter
  • bugfix: potential segfault when re_match() function was used
    Thanks to oxpa for the patch.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=371
  • bugfix: potential abort of imtcp on rsyslogd shutdown
  • bugfix: imzmq3 segfault with PULL subscription
    Thanks to Martin Nilsson for the patch.
  • bugfix: improper handling of backslash in string-type template()s
  • bugfix: leading quote (“) in string-type template() lead to thight loop
    on startup
  • bugfix: no error msg on invalid field option in legacy/string template
  • bugfix: potential segfault due to invalid param handling in comparisons
    This could happen in RainerScript comparisons (like contains); in some
    cases an unitialized variable was accessed, which could lead to an
    invalid free and in turn to a segfault.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=372
    Thanks to Georgi Georgiev for reporting this bug and his great help
    in solving it.
  • bugfix: no error msg on unreadable $IncludeConfig path
  • bugfix: $IncludeConfig did not correctly process directories
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=376
    The testbench was also enhanced to check for these cases.
    Thanks to Georgi Georgiev for the bug report.
  • bugfix: make rsyslog compile on kfreebsd again
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=380
    Thanks to Guillem Jover for the patch
  • bugfix: garbled message if field name was used with jsonf property option
    The length for the field name was invalidly computed, resulting in either
    truncated field names or including extra random data. If the random data
    contained NULs, the rest of the message became unreadable.
  • bugfix: potential segfault at startup with property-based filter
    If the property name was followed by a space before the comma, rsyslogd
    aborted on startup. Note that no segfault could happen if the initial
    startup went well (this was a problem with the config parser).
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=381
  • bugfix: imfile discarded some file parts
    File lines that were incomplete (LF missing) *at the time imfile polled
    the file* were partially discarded. That part of the line that was read
    without the LF was discarded, and the rest of the line was submitted in
    the next polling cycle. This is now changed so that the partial content
    is saved until the complete line is read. Note that the patch affects
    only read mode 0.
    Thanks to Milan Bartos for providing the base idea for the solution.
Scroll to top