| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
%$!all-json% will return a {}-wrapped object if there are are any
events, or when there is an attached (empty) pMsg->event, but an empty
string if nothing is attached. Let it return an empty object "{}" in
that case for consistency. In particular, this allows
$template MongoTemplate,"{%hostname:::jsonf:sys%, %$!all-json:2:$:%"
to always result in a valid JSON.
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
|
|
|
|
|
|
|
| |
JSON fields are "name":value, not "name"=value. Therefore change the
jsonf flag to use a colon.
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
action.c
configure.ac
doc/manual.html
runtime/ruleset.c
template.h
threads.c
tools/syslogd.c
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
template.c
|
| | |
| | |
| | |
| | |
| | | |
see template.c file header for details
Note that this functionality was almost never used in practice
|
| | | |
|
| | |
| | |
| | |
| | | |
Thanks to Andre Lorbach for mentioning this.
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
runtime/ruleset.c
|
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | | |
This is done to prevent name claches with libraries.
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
|\ \ \ \
| | |_|/
| |/| | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
some more elaborate patch is needed and will be provided
|
| | | | |
|
|\| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
... it could pass a NULL pointer to unlink. Depending on OS implementation,
this could (or could not...) lead to a segfault.
|
| | |/
| |/|
| | |
| | |
| | | |
...due to invalid mutex synchronisation in DA worker. In case of
idle queue, mutex was incorrectly locked.
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
The character immediately in front of the first escape was lost.
|
| | | | |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
plugins/omelasticsearch/omelasticsearch.c
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
makes JSON creation far more bulletproof (and also faster)
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |\ \ \ \ \
| | | |_|/ /
| | |/| | |
| | | | | |
| | | | | | |
Conflicts:
ChangeLog
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Thanks to Zdenek Salvet for finding this bug and to Bodik for reporting
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
For the time being, $uptime is not supported on Solaris
|
| |\| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |\ \ \ \ \ |
|
|\ \ \ \ \ \ \
| | |_|_|_|_|/
| |/| | | | |
| | | | | | |
| | | | | | | |
Conflicts:
runtime/modules.c
|
| |\ \ \ \ \ \
| | | |_|/ / /
| | |/| | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
runtime/modules.c
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
If it is not present, it must have the nilvalue "-" as of RFC5424
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=332
Thanks to John N for reporting this issue.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=316
Thanks to Andreas Piesk for reporting&analyzing this bug as well as
providing patches and other help in resolving it.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
also added some error checking
|
| | | |/ / /
| | |/| | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
traditional system line buffers were not freed. semi-static memory leak
during config load phase, did not grow while processing messages. Usually
less than 5k during the whole runtime.
|
|\| | | | | |
|
| |\| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
runtime/queue.c
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is a minor optimization to spare some cycles if the timeout
is set to immediate discard
|
|\| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
ChangeLog
|
| |\| | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
if rsyslog was set to auto-background (thus fork, the default) and debug
mode to stdout was enabled, debug messages ended up in the first log file
opened. Currently, stdout logging is completely disabled in forking mode
(but writing to the debug log file is still possible). This is a change
in behaviour, which is under review. If it causes problems to you,
please let us know.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
http://bugzilla.adiscon.com/show_bug.cgi?id=299
The new code also handles the case of shutdown of blocking light and
full delayable sources somewhat smarter and permits, assuming sufficient
timouts, to persist message up to the max queue capacity. Also some nits
debug instrumentation have been fixed.
|