- bugfix: some man pages were not properly installed either
rscryutil or rsgtutil man was installed, but not both.
Thanks to Marius Tomaschewski for the patch.
- bugfix: potential segfault on startup when builtin module was
specified in module() statement.
Thanks to Marius Tomaschewski for reporting the bug.
- bugfix: segfault due to invalid dynafile cache handling
Accidently, the old-style cache size parameter was used when the
dynafile cache was created in a RainerScript action. If the
old-style size was lower than the one actually set, this lead to
misadressing when the size was overrun, and that could lead to
all kinds of “interesting things”, often in segfaults.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=440
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=147
- Enable rsyslog.service and create the syslog.service alias link
in post install -- regardless of a preset config (bnc#790805).
- Check the existence of /etc/init.d/syslog script before calling
the restart_on_update and stop_on_removal macros to avoid errors
on update. Since openSUSE 12.3, no syslog init script is shipped
(bnc#90298,bnc#750478).
OBS-URL: https://build.opensuse.org/request/show/147807
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=122
- enhance: permit RFC3339 timestamp in local log socket messages
Thanks to Sebastien Ponce for the patch.
- imklog: added ParseKernelTimestamp parameter (import from 5.10.2)
Thanks to Marius Tomaschewski for the patch.
- fix missing functionality: ruleset(){} could not specify ruleset queue
The "queue.xxx" parameter set was not supported, and legacy ruleset
config statements did not work (by intention). The fix introduces the
"queue.xxx" parameter set. It has some regression potential, but only
for the new functionality. Note that using that interface it is possible
to specify duplicate queue file names, which will cause trouble. This
will be solved in v7.3, because there is a too-large regression
potential for the v7.2 stable branch.
- imklog: added KeepKernelTimestamp parameter (import from 5.10.2)
Thanks to Marius Tomaschewski for the patch.
- bugfix: imklog mistakenly took kernel timestamp subseconds as nanoseconds
... actually, they are microseconds. So the fractional part of the
timestamp was not properly formatted. (import from 5.10.2)
Thanks to Marius Tomaschewski for the bug report and the patch idea.
- bugfix: supportoctetcountedframing parameter did not work in imptcp
- bugfix: modules not (yet) supporting new conf format were not properly
registered. This lead to a "module not found" error message instead of
the to-be-expected "module does not support new style" error message.
That invalid error message could be quite misleading and actually stop
people from addressing the real problem (aka "go nuts" ;))
- bugfix: template "type" parameter is mandatory (but was not)
- bugfix: some message properties could be garbled due to race condition
This happened only on very high volume systems, if the same message was
being processed by two different actions. This was a regression caused
by the new config processor, which did no longer properly enable msg
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=120
forward of rq142533 to Base:System
- fix zeromq support
- fix hiredis support
- enabled elastic search support (build enabled by default):
-> new buildrequires curl devel
-> new subpackage rsyslog-module-elasticsearch
- added --enable-unlimited-select
- added --enable-imttcp:
-> this module is packaged in the main package as it has no
new dependencies
- added --enable-imdiag
-> this module is packaged in the diag package
- prepared adding support for hiredis, hdfs, mongodb and zeromq
OBS-URL: https://build.opensuse.org/request/show/142910
OBS-URL: https://build.opensuse.org/package/show/Base:System/rsyslog?expand=0&rev=118
- 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
