| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
it now truncates these message, but ensures they are sent. Note that
7.2.5+ will switch to fragmented UDP messages instead (up to 64K)
|
| |
|
| |
|
|
|
|
|
|
| |
... actually, they are microseconds. So the fractional part of the
timestamp was not properly formatted.
Thanks to Marius Tomaschwesky for the bug report and the patch idea.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This happened only under some circumstances. Thanks to Marius
Tomaschwesky, Florian Piekert and Milan Bartos for their help in
solving this issue.
Note that Milan sent a patch, which solved the problem under some
conditions (can be found somewhat earlier in git history). However,
it did not handle the original root cause, and so did not fix the
problem always. The main reason was that the date parser modifies
the provided lenghts. That part of the API was not properly
used by the caller (who decremented the length once more).
|
|
|
|
|
|
|
| |
Thanks to Michael Biebl for identifying this as the culprit for
several build-related issues. The plugin is a placeholder, and was
not used for quite some while. It is definitely not worth the effort
to keep it along. If needed, can be quickly created.
|
|
|
|
|
| |
The problem occured when using the -f (dynafiles) option,
and caused some tests to fail.
|
| |
|
|
|
|
|
|
| |
...if action chaining (& operator) was used
http://bugzilla.adiscon.com/show_bug.cgi?id=355
Thanks to pilou@gmx.com for the bug report
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | |
|
|\|
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
some more elaborate patch is needed and will be provided
|
| |
| |
| |
| |
| |
| |
| | |
note that none of the rsyslog-provided plugins does this
Thanks to bodik and Rohit Prasad for alerting us on this bug and
analyzing it.
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=347
|
| | |
|
| |
| |
| |
| |
| | |
...due to invalid mutex synchronisation in DA worker. In case of
idle queue, mutex was incorrectly locked.
|
|\| |
|
| |
| |
| |
| |
| | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=327
Thanks to Rick Brown for helping to test out the patch.
|
| |
| |
| |
| |
| | |
Thanks to bodik for reporting this bug.
---------------------------------------------
|
|\|
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| |
| |
| |
| | |
Thanks to Zdenek Salvet for finding this bug and to Bodik for reporting
|
|\|
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| | |
There seem to be cases where the shutdown message is otherwise not
processed, not even on an idle system. Thanks to Marcin for
bringing this problem up.
|
| | |
|
|\|
| |
| |
| |
| | |
Conflicts:
runtime/queue.c
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
even if there was a disk queue associated with it. The root cause of this
problem was that it makes no sense to delay messages once they arrive in the
action queue - the "input" that is being held in that case is the main
queue worker, what makes no sense.
Thanks to Marcin for alerting us on this problem and providing
instructions to reproduce it.
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| | |
threads.
Root cause is that libnet is not thread-safe. Omudpspoof now
guards libnet calls with their own mutex.
|
|\|
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
in debug instrumentation have been fixed.
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\ \ |
|
| | | |
|
|\ \ \
| |/ /
|/| /
| |/
| | |
Conflicts:
ChangeLog
|
| | |
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
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).
|