stable

Version 4.2.0 [v4-stable] (rgerhards), 2009-06-23

• bugfix: light and full delay watermarks had invalid values, badly affecting performance for delayable inputs
• bugfix: compile problems in im3195
• imported all patches from 3.22.1 as of today (see below):
  • bugfix: invalid error message issued if $inlcudeConfig was on an empty set of files (e.g. *.conf, where none such files existed) thanks to Michael Biebl for reporting this bug
  • bugfix: when run in foreground (but not in debug mode), a debug message (“DoDie called”) was emitted at shutdown. Removed. thanks to Michael Biebl for reporting this bug
  • bugfix: some garbagge was emitted to stderr on shutdown. This garbage consisted of file names, which were written during startup (key point: not a pointer error) thanks to Michael Biebl for reporting this bug
  • bugfix: startup and shutdown message were emitted to stdout
    thanks to Michael Biebl for reporting this bug
  • bugfix: error messages were not emitted to stderr in forked mode (stderr and stdo are now kept open across forks)
  • bugfix: internal messages were emitted to whatever file had fd2 when rsyslogd ran in forked mode (as usual!) Thanks to varmojfekoj for the patch
  • small enhancement: config validation run now exits with code 1 if an error is detected. This change is considered important but small enough to apply it directly to the stable version. [But it is a border case, the change requires more code than I had hoped. Thus I have NOT tried to actually catch all cases, this is left for the current devel releases, if necessary]
  • bugfix: light and full delay watermarks had invalid values, badly affecting performance for delayable inputs
  • bugfix: potential segfault issue when multiple $UDPServerRun directives are specified. Thanks to Michael Biebl for helping to debug this one.
  • relaxed GnuTLS version requirement to 1.4.0 after confirmation from the field that this version is sufficient
  • bugfix: parser did not properly handle empty structured data

As a reminder:

Version 4.1.0 [DEVEL] (rgerhards), 2008-11-18

********************************* WARNING *********************************
This version has a slightly different on-disk format for message entries.
As a consequence, old queue files being read by this version may have
an invalid output timestamp, which could result to some malfunction inside
the output driver. It is recommended to drain queues with the previous
version before switching to this one.
********************************* WARNING *********************************

• greatly enhanced performance when compared to v3.
• added configuration directive “HUPisRestart” which enables to configure
  HUP to be either a full restart or “just” a leightweight way to
  close open files.
• enhanced legacy syslog parser to detect year if part of the timestamp
  the format is based on what Cisco devices seem to emit.
• added a setting “$OptimizeForUniprocessor” to enable users to turn off
  pthread_yield calls which are counter-productive on multiprocessor
  machines (but have been shown to be useful on uniprocessors)
• reordered imudp processing. Message parsing is now done as part of main
  message queue worker processing (was part of the input thread)
  This should also improve performance, as potentially more work is
  done in parallel.
• bugfix: compressed syslog messages could be slightly mis-uncompressed
  if the last byte of the compressed record was a NUL
• added $UDPServerTimeRequery option which enables to work with
  less acurate timestamps in favor of performance. This enables querying
  of the time only every n-th time if imudp is running in the tight
  receive loop (aka receiving messsages at a high rate)
• doc bugfix: queue doc had wrong parameter name for setting controlling
  worker thread shutdown period
• restructured rsyslog.conf documentation
• bugfix: memory leak in ompgsql
  Thanks to Ken for providing the patch

Version 3.22.0 [v3-stable] (rgerhards), 2009-04-21 This is the first stable release that includes the full functionality of the 3.21.x version tree.

• bugfix: $InputTCPMaxSessions config directive was accepted, but not honored. This resulted in a fixed upper limit of 200 connections.
• bugfix: the default for $DirCreateMode was 0644, and as such wrong. It has now been changed to 0700. For some background, please see http://lists.adiscon.net/pipermail/rsyslog/2009-April/001986.html
• bugfix: ompgsql did not detect problems in sql command execution this could cause loss of messages. The handling was correct if the connection broke, but not if there was a problem with statement execution. The most probable case for such a case would be invalid sql inside the template, and this is now much easier to diagnose.

Version 3.20.6 [v3-stable] (rgerhards), 2009-04-16

• this is the last v3-stable for the 3.20.x series
• bugfix: $InputTCPMaxSessions config directive was accepted, but not honored. This resulted in a fixed upper limit of 200 connections.
• bugfix: the default for $DirCreateMode was 0644, and as such wrong. It has now been changed to 0700. For some background, please see http://lists.adiscon.net/pipermail/rsyslog/2009-April/001986.html
  

Version 2.0.7 V2-STABLE (rgerhards), 2008-04-14

• bugfix: the default for $DirCreateMode was 0644, and as such wrong. It has now been changed to 0700. For some background, please see http://lists.adiscon.net/pipermail/rsyslog/2009-April/001986.html
• bugfix: “$CreateDirs off” also disabled file creation. Thanks to William Tisater for analyzing this bug and providing a patch.
  The actual code change is heavily based on William’s patch.

• bugfix: memory leak in ompgsql
  Thanks to Ken for providing the patch

• bugfix: potential memory leak in msg.c
  This one did not surface yet and the issue was actually found due to
  a problem in v4 – but better fix it here, too

Version 3.20.5 [v3-stable] (rgerhards), 2009-04-02

• bugfix: potential abort with DA queue after high watermark is reached
  There exists a race condition that can lead to a segfault. Thanks
  go to vbernetr, who performed the analysis and provided patch, which
  I only tweaked a very little bit.

• fixed bugs in RainerScript:
  • when converting a number and a string to a common type, both were
    actually converted to the other variable’s type.

  • the value of rsCStrConvertToNumber() was miscalculated.
    Thanks to varmojfekoj for the patch
• fixed a bug in configure.ac which resulted in problems with
  environment detection – thanks to Michael Biebl for the patch

• fixed a potential segfault problem in gssapi code
  thanks to varmojfekoj for the patch

• doc enhance: provide standard template for MySQL module and instructions
  on how to modify schema

Version 3.20.4 [v3-stable] (rgerhards), 2009-02-09

• bugfix: inconsistent use of mutex/atomic operations could cause segfault
  details are too many, for full analysis see blog post at:
  http://blog.gerhards.net/2009/01/rsyslog-data-race-analysis.html

• bugfix: invalid ./configure settings for RFC3195
  thanks to Michael Biebl for the patch

• bugfix: invalid mutex access in msg.c
• doc bugfix: dist tarball missed 2 files, had one extra file that no
  longer belongs into it. Thanks to Michael Biebl for pointing this out.

Version 3.20.3 [v3-stable] (rgerhards), 2009-01-19

• doc bugfix: v3-compatiblity document had typo in config directive
  thanks to Andrej for reporting this

• fixed a potential segfault condition with $AllowedSender directive
  On HUP, the root pointers were not properly cleaned up. Thanks to
  Michael Biebel, olgoat, and Juha Koho for reporting and analyzing
  the bug.

Version 3.20.0 [v3-stable] (rgerhards), 2008-11-05

• this is the inital release of the 3.19.x branch as a stable release
• bugfix: double-free in pctp netstream driver. Thank to varmojfeko
  for the patch

Version 3.18.5 (rgerhards), 2008-10-09

• bugfix: imudp input module could cause segfault on HUP
  It did not properly de-init a variable acting as a linked list head.
  That resulted in trying to access freed memory blocks after the HUP.

• bugfix: rsyslogd could hang on HUP
  because getnameinfo() is not cancel-safe, but was not guarded against
  being cancelled. pthread_cancel() is routinely being called during
  HUP processing.

• bugfix[minor]: if queue size reached light_delay mark, enqueuing
  could potentially be blocked for a longer period of time, which
  was not the behaviour desired.

• doc bugfix: $ActionExecOnlyWhenPreviousIsSuspended was still misspelled
  as $…OnlyIfPrev… in some parts of the documentation. Thanks to
  Lorenzo M. Catucci for reporting this bug.

• added doc on malformed messages, cause and how to work-around, to the
  doc set

• added doc on how to build from source repository

Version 3.18.4 (rgerhards), 2008-09-18

• bugfix: order-of magnitude issue with base-10 size definitions
  in config file parser. Could lead to invalid sizes, constraints
  etc for e.g. queue files and any other object whose size was specified
  in base-10 entities. Did not apply to binary entities. Thanks to
  RB for finding this bug and providing a patch.

• bugfix: action was not called when system time was set backwards
  (until the previous time was reached again). There are still some
  side-effects when time is rolled back (A time rollback is really a bad
  thing to do, ideally the OS should issue pseudo time (like NetWare did)
  when the user tries to roll back time). Thanks to varmojfekoj for this
  patch.

• doc bugfix: rsyslog.conf man page improved and minor nit fixed
  thanks to Lukas Kuklinek for the patch.

• bugfix: error code -2025 was used for two different errors. queue full
  is now -2074 and -2025 is unique again. (did cause no real problem
  except for troubleshooting)

• bugfix: default discard severity was incorrectly set to 4, which lead
  to discard-on-queue-full to be enabled by default. That could cause
  message loss where non was expected. The default has now been changed
  to the correct value of 8, which disables the functionality. This
  problem applied both to the main message queue and the action queues.
  Thanks to Raoul Bhatia for pointing out this problem.

• bugfix: option value for legacy -a option could not be specified,
  resulting in strange operations. Thanks to Marius Tomaschewski
  for the patch.

• bugfix: colon after date should be ignored, but was not. This has
  now been corrected. Required change to the internal ParseTIMESTAMP3164()
  interface.