Version 8.38.0 [v8-stable] 2018-09-18
- AIX: make basic modules work again
- make rsyslog build on AIX again
- imfile: support for endmsg.regex
- imkafka: add parameter "parseHostName"
- im[p]tcp: improve error message on connect failure
- imkafka: implement multithreading support for kafka consumers.
- omelasticsearch: write all header metadata to $.omes for retries
- core: improve error message on module load fail
- core/queue: add error message if queue file cannot be accessed
- imtcp/imudp: new option preservecase for managing the case of
FROMHOST value
- omprog: add feedback timeout and keep-alive feature
- omprog: fix forceSingleInstance configuration option
- imfile: implement file-id, used in state file
- imfile: experimental input throtteling feature
- core: emit TZ warning on startup not on Linux non-container
- omkafka:
- better debug information
- Fixed minor issue in omkafka producing wrong kafka timestamps when
msgTimestamp was NULL.
- Setting RD_KAFKA_V_KEY(NULL, 0) in rd_kafka_producev now when KEY
is not configured.
- Fixed minor issue when rsyslog is compiled with --enable-debug and
librdkafka is too old.
- omfile bugfix: errant error message when dynafile param needed
- omhttp: new contribued module
- mmkubertnetes: action fails preparation cycle if kubernetes API
destroys resource during bootup sequence
- bugfix pmnormalize/core: several memory leaks, invld property
handling
- bugfix imptcp: fixed pointers for session counting
- bugfix omprog: invalid memory access on partial writes to pipe
- bugfix omprog: rsyslog's environment was not passed to script
- bugfix omprog: severity of some log messages in waitForChild
corrected
- bugfix imfile: files which were loaded via symlink were not always
followed
- bugfix imfile: potential misadressing when processing symlinks
- bugfix ommongodb: build issue if mongo-c-driver is not compiled with
TLS
- imptcp: add ability to configure socket backlog
- omfile: do not permit filename that only consists of whitespace
- fmhash: new hash function module
- some better error messages
- imklog: add ratelimiting capability
- omkafka: added impstats counters for librdkafka returned statistics
- imudp
* use rsyslog message rate-limiter instead of home-grown one
* add stats counter "disallowed"
- imrelp: add parameter "oversizeMode"
- core: consistent handling of oversize input messages
- omfwd: add support for bind-to-address for UDP
- template systemd service file proposes higher permitted file handle
limit
- imuxsock: replace select() call by poll()
- nsdsel_ptcp: replace select() by poll()
- omprog: refactor tests, fix child closing issues
- core: config optimizer did not handle call_indirect
- debug support: add capability to print testbench-specific timeout
reports
- mmgrok: fix potential segfault
- imrelp bugfix: maxDataSize could be set lower than maxMessageSize
- build system bugfix: build broken if liblogging-stdlog installed in
custom path
- core bugfix: segfault on queue shutdown
- imfile bugfix: statefiles contain invalid JSON
- omfile bugfix: segfault if empty filename was given
- fix build issues when atomic operations are not present
- lmsig_ksils12 bugfix: build and static analyzer issues
- impstats bugfix: segfault if bound to non-existing ruleset
- mmjsonparse bugfix: invalid container name was not detected
- mmkubernetes bugfixes: fix lnrules, add defaults, add test
- build system bugfix: --enable-atomic-operations did not work
- bugfix: rsyslog aborts on startup when specific config errors are
made
- build system: remove no longer needed --enable-libcurl configure
Version 8.22.0 [v8-stable] 2016-10-04
- ompgsql: add template support
Thanks to Radu Gheorghe for implementing this.
- generate somewhat better error message on config file syntax error
a common case (object at invalid location) has received it's own error
message; for the rest we still rely on the generic flex/bison handler
- bugfix:omhiredis reconnects after failure
previously it could loose messages under such conditions.
Thanks to Bob Gregory for the patch.
- general cleanup and code improvement
mostly guided by compiler warnings induced by newer opensuse builbot
environment
------------------------------------------------------------------------------
Version 8.21.0 [v8-stable] 2016-08-23
- CHANGE OF BEHAVIOUR:
by default, internal messages are no longer logged via the internal
bridge to rsyslog but via the syslog() API call [either directly or
via liblogging). For the typical single-rsyslogd-instance installation this
is mostly unnoticable (except for some additional latency). If multiple
instances are run, only the "main" (the one processing system log messages)
will see all messages. To return to the old behaviour, do either of those
two:
1) add in rsyslog.conf:
global(processInternalMessages="on")
2) export the environment variable RSYSLOG_DFLT_LOG_INTERNAL=1
This will set a new default - the value can still be overwritten via
rsyslog.conf (method 1). Note that the environment variable must be
set in your **startup script**.
For more information, please visit
http://www.rsyslog.com/rsyslog-error-reporting-improved/
- slightly improved TLS syslog error messages
- queue subsystem: improved robustness
The .qi file is now persisted whenever an existing queue file is fully
written and a new file is begun. This helps with rsyslog aborts, including
the common case where the OS issues kill -9 because of insufficiently
configured termination timout (this is an OS config error, but a frequent
one). Also, a situation where an orphaned empty file could be left in the
queue work directory has been fixed. We expect that this change causes
fewer permanent queue failures.
- bugfix: build failed on some platforms due to missing include files
Version 8.13.0 [v8-stable] 2015-09-22
- ZeroMQ enhancements:
- Added the ability to set a static publishing topic per action as an
alternative to constructing topics with templates
- ZMQ_PUB socket now defaults to bind and ZMQ_SUB socket now defaults to
connect
- Redis enhancements:
- Can now LPUSH to a Redis list in "queue" mode
- Can now PUBLISH to a Redis channel in "publish" mode
- build requirement for rsyslog/mmnormalize is now liblognorm 1.1.2 or above
- mmnormalize: liblognorm error messages are now emitted via regular
rsyslog error reporting mechanism (aka "are now logged")
- add support for TCP client side keep-alives
- bugfix: imtcp/TLS hangs on dropped packets
- bugfix testbench: some tests using imptcp are run if module is disabled
- bugfix omkafka: Fixes a bug not accepting new messages anymore.
- bugfix: Parallel build issue "cannot find ../runtime/.libs/librsyslog.a:
No such file or directory" (#479) fixed.
- bugfix: Added missing mmpstructdata testfiles into makefile.
- bugfix: Reverted FIX for issue #392 as it had unexpected side effects.
- The new fix duplicates the Listener object for static files (like
done for dynamic files already), resolving issue #392 and #490.
- bugfix: issues in queue subsystem if syncqueuefiles was enabled
- Error 14 was generated on the .qi file directory handle.
As the .qi filestream does not have a directory set, fsync
was called on an empty directory causing a error 14 in debug log.
- When queue files existed on startup, the bSyncQueueFiles
strm property was not set to 1. This is now done in the
qqueueLoadPersStrmInfoFixup function.
- bugfix/testbench: tcpflood tool could abort when random data was added
- rscryutil: Added support to decrypt a not closed log file.
Rsyslog is an enhanced syslogd supporting, among others, MySQL,
PostgreSQL, failover log destinations, syslog/tcp, fine grain
output format control, high precision timestamps, queued operations
and the ability to filter on any message part. It is quite
compatible to stock sysklogd and can be used as a drop-in
replacement.