- bugfix: ruleset()-object did only support a single statement
- added -D rsyslogd option to enable config parser debug mode
- improved syntax error messages by outputting the error token
- the rsyslog core now suspeneds actions after 10 failures in
a row. This was former the case after 1,000 failures and could
cause rsyslog to be spammed/ressources misused.
See the v6 compatibility doc for more details.
- ommongodb rate-limits error messages to prevent spamming the
syslog closes (for v7.2):
http://bugzilla.adiscon.com/show_bug.cgi?id=366
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=106
version which provides following features compared to v5-stable:
* greatly improved configuration language – the new language is
much more intuitive than the legacy format. It will also prevent
some typical mistakes simply be not permitting these invalid
constructs. Note that legacy format is still fully supported
(and you can of course do the same mistakes if you use legacy
format).
* greatly improved execution engine – with nested if/then/else
constructs as well as the capability to modify variables during
processing.
* full support for structured logging and project lumberjack/CEE.
this includes everything from being able to create, interpret
and handle JSON-based structured log messages, including the
ability to normalize legacy text log messages.
* more plugins – like support for MongoDB, HDFS, and ElasticSearch
as well as for the kernel’s new structured logging system.
* higher performance – many optimizations all over the code, like
5 to 10 times faster execution time for script-based filters,
enhanced multithreaded TCP input plugin, DNS cache and many more.
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=104
multiple facilities with the same priority pattern in one
statement using the comma operator. This started to cause a
start failure with rsyslog-6.4.x (bnc#780607) and seems to
be a bug in rsyslog (upstream verify in progress).
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=96
- bugfix: multiple main queues with same queue file name were not
detected. This lead to queue file corruption. While the root
cause is a config error, it is a bug that this important and
hard to find config error was not detected by rsyslog.
- bugfix: “jsonf” property replacer option did generate invalid
JSON in JSON, we have “fieldname”:”value”, but the option
emitted “fieldname”=”value”. Interestingly, this was accepted
by a couple of sinks, most importantly elasticsearch. Now the
correct format is emitted, which causes a remote chance that
some things that relied on the wrong format will break.
Thanks to Miloslav Trmač for the patch
- change $!all-json did emit an empty (thus non-JSON) string if
no libee data was present. It now emits {} and thus valid JSON.
There is a small risk that this may break some things that
relied on the previous inconsistency. Thanks to Miloslav Trmač
for the patch
- bugfix: omusrsmsg incorrect return state & config warning
handling. During config file processing, Omusrmsg often
incorrectly returned a warning status, even when no warning was
present (caused by uninitialized variable). Also, the core
handled warning messages incorrectly, and treated them as
errors. As a result, omusrmsg (most often) could not properly be
loaded. Note that this only occurs with legacy config action
syntax. This was a regression caused by an incorrect merge in to
the 6.3.x codebase.
Thanks to Stefano Mason for alerting us of this bug.
- bugfix: Fixed TCP CheckConnection handling in omfwd.c. Interface
needed to be changed in lower stream classes. Syslog TCP Sending
is now resumed properly. Unfixed, that lead to non-detection of
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=93
- bugfix: ommysql did not properly init/exit the mysql runtime
library this could lead to segfaults. Triggering condition:
multiple action instances using ommysql. Thanks to Tomas
Heinrich for reporting this problem and providing an initial
patch (which my solution is based on, I need to add more code
to clean the mess up).
- bugfix: rsyslog did not terminate when delayable inputs were
blocked due to unvailable sources. Fixes:
http://bugzilla.adiscon.com/show_bug.cgi?id=299
Thanks to Marcin M for bringing up this problem and Andre
Lorbach for helping to reproduce and fix it.
- bugfix: active input in “light delay state” could block
rsyslog termination, at least for prolonged period of time
- bugfix: imptcp input name could not be set. Config directive
was accepted, but had no effect
bugfix: assigned ruleset was lost when using disk queues
This looked quite hard to diagnose for disk-assisted queues,
as the pure memory part worked well, but ruleset info was lost
for messages stored inside the disk queue.
- bugfix: hostname was not requeried on HUP
Thanks to Per Jessen for reporting this bug and Marius
Tomaschewski for his help in testing the fix.
- bugfix: inside queue.c, some thread cancel states were not
correctly reset. While this is a bug, we assume it did have
no practical effect because the reset as it was done was set
to the state the code actually had at this point. But better
fix this…
- Removed obsolete requery hostname patch
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=82
- bugfix: instabilities when using RFC5424 header fields
Thanks to Kaiwang Chen for the patch
- bugfix: imuxsock did truncate part of received message if it did
not contain a proper date. The truncation occured because we
removed that part of the messages that was expected to be the date.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=295
- bugfix: potential abort after reading invalid X.509 certificate
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=290
Thanks to Tomas Heinrich for the patch
- bugfix: stats counter were not properly initialized on creation
- FQDN hostname for multihomed host was not always set to the correct
name if multiple aliases existed. Thanks to Tomas Heinreich for the
patch.
- updated to 5.8.6 [V5-stable]:
- bugfix: missing whitespace after property-based filter was not
detected
- bugfix: $OMFileFlushInterval period was doubled - now using correct
value
- bugfix: ActionQueue could malfunction due to index error
Thanks to Vlad Grigorescu for the patch
- bugfix: $ActionExecOnlyOnce interval did not work properly
Thanks to Tomas Heinrich for the patch
- bugfix: race condition when extracting program name, APPNAME,
structured data and PROCID (RFC5424 fields) could lead to invalid
characters e.g. in dynamic file names or during forwarding (general
malfunction ofthese fields in templates, mostly under heavy load)
- bugfix: imuxsock did no longer ignore message-provided timestamp,
if so configured (the *default*). Lead to no longer sub-second
timestamps.
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=76
file, marked the /etc/rsyslog.early.conf obsolete.
Note: rsyslog will be started early/before network using its normal
/etc/rsyslog.conf config file (adopted scripts in syslog-service
package). When any kind of remote logging is in use, then on-disk
queues should be enabled. To start it after the network, please set
the SYSLOG_REQUIRES_NETWORK=yes variable in /etc/sysconfig/syslog
(bnc#728565).
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=74
- bugfix/security: off-by-two bug in legacy syslog parser,
CVE-2011-3200 bnc#714658
- bugfix: mark message processing did not work correctly
- bugfix: potential hang condition during tag emulation
- bugfix: too-early string termination during tag emulation
- bugfix: The NUL-Byte for the syslogtag was not copied in MsgDup
(msg.c)
- bugfix: fixed incorrect state handling for Discard Action
(transactions) Note: This caused all messages in a batch to be
set to COMMITTED, even if they were discarded.
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=71
- Update to 5.8.4 [V5-stable]
- bugfix: potential misadressing in property replacer
- bugfix: memcpy overflow can occur in allowed sender checkig if
a name is resolved to IPv4-mapped-on-IPv6 address Found by
Ismail Dönmez at suse
- bugfix: potential misadressing in property replacer
- bugfix: MSGID corruption in RFC5424 parser under some
circumstances closes:
http://bugzilla.adiscon.com/show_bug.cgi?id=275
- remove rsyslog-5.8.0-memcpy.patch:
applied upstream
- fix build for older distros:
only buildrequire systemd-devel for newer than 11.4, use systemd
for the others
OBS-URL: https://build.opensuse.org/request/show/79342
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=67
- drop modules imtemplate and omtemplate, the 2 modules are base
templates for people who want to develop their own modules.
- enabled a few more modules which dont pull extra dependencies:
impstats, pmcisconames, pmaixforwardedfrom, pmsnare, pmrfc3164sd,
omruleset, mmsnmptrapd
- guard the file list entry for rsyslog.service with
if {with systemd}. Please keep the package working on older
distros.
- upstream asked to change the syntax in the default config files
to the new syntax:
old: *.* * # (write to all)
new: *.* :omusrmsg:*
old: *.* $channel
new: *.* :omfile:$channel
from what i can see we are only affected with:
old: *.emerg *
new: *.emerg :omusrmsg:*
- Updated to 5.8.3 [V5-stable]
OBS-URL: https://build.opensuse.org/request/show/76171
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=62
* action processor released mememory too early, resulting in
potential issue in retry cases (very unlikely).
* batch processing flagged invalid message as "bad" under some
circumstances
* unitialized variable could cause issues under extreme
conditions plus some minor nits.
* batches which had actions in error were not properly retried
in all cases
* imfile did duplicate messages under some circumstances
- enabled plain tcp input, unix socket output, last message
parser and the libdbi module as separate package.
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=36
* compile failed on systems without epoll_create1()
Thanks to David Hill for providing a fix.
* atomic increment for msg object may not work correct on
all platforms. Thanks to Chris Metcalf for the patch
* replacements for atomic operations for non-int sized types
had problems. At least one instance of that problem could
potentially lead to abort (inside omfile).
- Increased mark frequency in rsyslog.conf to 1 hour
- Enabled duplicate message reduction in rsyslog.conf to catch
at least buggy programs running amok and writting same message
zillion times until the disk gets out of space (bnc#656197).
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=30
a new stable series based on the 5.3.x series, which has been
proven rather well in practice. The new 5.4.0 contains fixes for
all known problems. See ChangeLog file for a detailed history.
The main new feature is speed: several optimizations were done,
including support for epoll in tcp listeners.
- Added new lmzlibw.so and omruleset.so to the file list.
- Recompressed original tar.gz source archive using bzip2.
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=12
enancements and bug fixes. Digest from the ChangeLog file:
* new feature: $OMFileAsyncWriting directive added
* bugfix(temporary): message-induced off-by-one error (potential
segfault). As a temporary fix, we have introduced a proper
recalculation of the size. However, a final patch is expected
in the future. See bug tracker for further details and when
the final patch will be available: bug id 184
* bugfix: potential segfault in dynafile cache
* bugfix: race condition during directory creation
* bugfix: potential re-use of free()ed file stream in omfile
* added new property replacer option "date-rfc3164-buggyday"
primarily to ease migration from syslog-ng
* bugfix: invalid buffer write in (file) stream class
* bugfix: potential hang condition during filestream close
* bugfix: improper synchronization when "$OMFileFlushOnTXEnd on"
* bugfix: potential data loss during file stream shutdown
* bugfix: potential problem (loop, abort) on file write error
* bugfix: $omfileFlushOnTXEnd was turned on when set to off
* bugfix(minor): handling of extremely large strings in dbgprintf
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=11
providing some important fixes for issues that have only been
detected after the beta phase. Some of them are serious (like a
segfault when UDP messageforwarding is activated), so users of
4.4.0 are urged to upgrade to this release. Changelog for 4.4.1:
* features requiring Java are automatically disabled if Java
is not present (thanks to Michael Biebl for his help!)
* bugfix: invalid double-quoted PRI, among others in outgoing
messages. This causes grief with all receivers.
Bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=147
* bugfix: Java testing tools were required, even if testbench
was disabled. This resulted in build errors if no Java was
present on the build system, even though none of the selected
option actually required Java. (I forgot to backport a similar
fix to newer releases).
* bugfix (backport): omfwd segfault. Note that the orginal (higher
version) patch states this happens only when debugging mode is
turned on. That statement is wrong: if debug mode is turned off,
the message is not being emitted, but the division by zero in
the actual parameters still happens.
- Removed jave2-devel-packages from build requires again
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=6
