Search Results for: libfastjson

Version 8.17.0 [v8-stable] 2016-03-08

• NEW REQUIREMENT: libfastjson
  see also:
  http://blog.gerhards.net/2015/12/rsyslog-and-liblognorm-will-switch-to.html
• new testbench requirement: faketime command line tool
  This is used to generate a controlled environment for time-based tests; if
  not available, tests will gracefully be skipped.
• improve json variable performance
  We use libfastjson’s alternative hash function, which has been
  proven to be much faster than the default one (which stems
  back to libjson-c). This should bring an overall performance
  improvement for all operations involving variable processing.
  closes https://github.com/rsyslog/rsyslog/issues/848
• new experimental feature: lookup table suport
  Note that at this time, this is an experimental feature which is not yet
  fully supported by the rsyslog team. It is introduced in order to gain
  more feedback and to make it available as early as possible because many
  people consider it useful.
  Thanks to Janmejay Singh for implementing this feature
• new feature: dynamic statistics counters
  which may be changed during rule processing
  Thanks to Janmejay Singh for suggesting and implementing this feature
• new contributed plugin: omampq1 for AMQP 1.0-compliant brokers
  Thanks to Ken Giusti for this module
• new set of UTC-based $now family of variables ($now-utc, $year-utc, …)
• simplified locking when accessing message and local variables
  this simlifies the code and slightly increases performance if such
  variables are heavily accessed.
• new global parameter “debug.unloadModules”
  This permits to disable unloading of modules, e.g. to make valgrind
  reports more useful (without a need to recompile).
• timestamp handling: guard against invalid dates
  We do not permit dates outside of the year 1970..2100
  interval. Note that network-receivers do already guard
  against this, so the new guard only guards against invalid
  system time.
• imfile: add “trimlineoverbytes” input paramter
  Thanks to github user JindongChen for the patch.
• ommongodb: add support for extended json format for dates
  Thanks to Florian Bücklers for the patch.
• omjournal: add support for templates
  see also: https://github.com/rsyslog/rsyslog/pull/770
  Thanks to github user bobthemighty for the patch
• imuxsock: add “ruleset” input parameter
• testbench: framework improvement: configs can be included in test file
  they do no longer need to be in a separate file, which saves a bit
  of work when working with them. This is supported for simple tests with
  a single running rsyslog instance
  Thanks to Janmejay Singh for inspiring me with a similar method in
  liblognorm testbench.
• imptcp: performance improvements
  Thanks to Janmejay Singh for implementing this improvement
• made build compile (almost) without warnings
  still some warnings are suppressed where this is currently required
• improve interface definition in some modules, e.g. mmanon, mmsequence
  This is more an internal cleanup and should have no actual affect to
  the end user.
• solaris build: MAXHOSTNAMELEN properly detected
• build system improvement: ability to detect old hiredis libs
  This permits to automatically build omhiredis on systems where the
  hiredis libs do not provide a pkgconfig file. Previsouly, this
  required manual configuration.
  Thanks to github user jaymell for the patch.
• rsgtutil: dump mode improvements
  • auto-detect signature file type
  • ability to dump hash chains for log extraction files
• build system: fix build issues with clang
  clang builds often failed with a missing external symbol
  “rpl_malloc”. This was caused by checks in configure.ac,
  which checked for specific GNU semantics. As we do not need
  them (we never ask malloc for zero bytes), we can safely
  remove the macros.
  Note that we routinely run clang static analyer in CI and
  it also detects such calls as invalid.
  closes https://github.com/rsyslog/rsyslog/issues/834
• bugfix: unixtimestamp date format was incorrectly computed
  The problem happened in leap year from March til then end
  of year and healed itself at the begining of the next year.
  During the problem period, the timestamp was 24 hours too low.
  fixes https://github.com/rsyslog/rsyslog/issues/830
• bugfix: date-ordinal date format was incorrectly computed
  same root cause aus for unixtimestamp and same triggering
  condition. During the affected perido, the ordinal was one
  too less.
• bugfix: some race when shutting down input module threads
  this had little, if at all, effect on real deployments as it resulted
  in a small leak right before rsyslog termination. However, it caused
  trouble with the testbench (and other QA tools).
  Thanks to Peter Portante for the patch and both Peter and Janmejay
  Singh for helping to analyze what was going on.
• bugfix tcpflood: did not handle connection drops correct in TLS case
  note that tcpflood is a testbench too. The bug caused some testbench
  instability, but had no effect on deplyments.
• bugfix: abort if global parameter value was wrong
  If so, the abort happened during startup. Once started,
  all was stable.
• bugfix omkafka: fix potential NULL pointer addressing
  this happened when the topic cache was full and an entry
  needed to be evicted
• bugfix impstats: @cee cookie was prefixed to wrong fromat (json vs. cee)
  Thanks to Volker Fröhlich for the fix.
• bugfix imfile: fix race during startup that could lead to some duplication
  If a to-be-monitored file was created after inotify was initialized
  but before startup was completed, the first chunk of data from this
  file could be duplicated. This should have happened very rarely in
  practice, but caused occasional testbench failures.
  see also: https://github.com/rsyslog/rsyslog/issues/791
• bugfix: potential loss of single message at queue shutdown
  see also: https://github.com/rsyslog/rsyslog/issues/262
• bugfix: potential deadlock with heavy variable access
  When making havy use of global, local and message variables, a deadlock
  could occur. While it is extremly unlikely to happen, we have at least
  seen one incarnation of this problem in practice.
• bugfix ommysql: on some platforms, serverport parameter had no effect
  This was caused by an invalid code sequence which’s outcome depends on
  compiler settings.
• bugfix omelasticsearch: invalid pointer dereference
  The actual practical impact is not clear. This came up when working
  on compiler warnings.
  Thanks to David Lang for the patch.
• bugfix omhiredis: serverport config parameter did not reliably work
  depended on environment/compiler used to build
• bugfix rsgtutil: -h command line option did not work
  Thanks to Henri Lakk for the patch.
• bugfix lexer: hex numbers were not properly represented
  see: https://github.com/rsyslog/rsyslog/pull/771
  Thanks to Sam Hanes for the patch.
• bugfix TLS syslog: intermittent errors while sending data
  Regression from commit 1394e0b. A symptom often seen was the message
  “unexpected GnuTLS error -50 in nsd_gtls.c:530”
• bugfix imfile: abort on startup if no slash was present in file name param
  Thanks to Brian Knox for the patch.
• bugfix rsgtutil: fixed abort when using short command line options
  Thanks to Henri Lakk
• bugfix rsgtutil: invalid computation of log record extraction file
  This caused verification to fail because the hash chain was actually
  incorrect. Depended on the input data set.
  closes https://github.com/rsyslog/rsyslog/issues/832
• bugfix build system: KSI components could only be build if in default path