| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
| |
| |
| | |
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
|
| | |
|
| |
| |
| |
| |
| | |
... 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.
|
| |
| |
| |
| | |
This is done to prevent name claches with libraries.
|
|\| |
|
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| | |
This is a minor optimization to spare some cycles if the timeout
is set to immediate discard
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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).
|
| |
| |
| |
| |
| |
| |
| | |
...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.
|
| |
| |
| |
| |
| |
| | |
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...
|
| | |
|
| |
| |
| |
| | |
at least for prolonged period of time...
|
| | |
|
|\ \ |
|