| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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...
|
|
|
|
| |
again, credits to Jo Rhett for reporting this issue
|
|
|
|
| |
Thanks to Jo Rhett for reporting the bug.
|
| |
|
|
|
|
|
|
| |
bugfix: imptcp input name could not be set
config directive was accepted, but had no effect
|
|
|
|
|
| |
actually a regression from last bugfix - I just wonder why the other
machine did not complain :-S
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Signed-off-by: Marius Tomaschewski <mt@suse.com>
|
|
|
|
|
|
|
|
| |
LocalDomain points to "" or the domain in LocalHostName,
allocate as new string before passing to SetLocalDomain
or free will fail later.
Signed-off-by: Marius Tomaschewski <mt@suse.com>
|
| |
|
|
|
|
| |
Thanks to Marius Tomaschewski for reporting this bug.
|
| |
|
|
|
|
|
|
| |
queue config
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| |
|
|
|
|
| |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
...due to a regression from statistics module.
|
| |
|
|
|
|
|
| |
Changed to check "/run/systemd/journal" directory and not the
socket, as the socket may not exists [e.g. is not activated].
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From the syslog.socket unit file of newer systemd versions:
The default syslog implementation should make syslog.service a
symlink to itself, so that this socket activates the right actual
syslog service.
Examples:
/etc/systemd/system/syslog.service ->
/lib/systemd/system/rsyslog.service
/etc/systemd/system/syslog.service ->
/lib/systemd/system/syslog-ng.service
Best way to achieve that is by adding this to your unit file
(i.e. to rsyslog.service or syslog-ng.service):
[Install]
Alias=syslog.service
http://cgit.freedesktop.org/systemd/systemd/tree/units/syslog.socket#n26
|
|
|
|
|
|
|
| |
Detect if we have to use the new /run/systemd/journal/syslog
socket instead of the /dev/log under newer systemd versions.
Signed-off-by: Marius Tomaschewski <mt@suse.com>
|
|
|
|
| |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=313
|
|\ |
|
| |
| |
| |
| | |
after getting OK via email from contributor Ariel P. (2012-02-02 22:06 CET)
|
| | |
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
configured
|
| |
| |
| |
| |
| | |
after receiving permission from Red Hat legal (given in email from
Tomas Heinrich)
|
| |
| |
| |
| |
| | |
We now also emit an error message if even 64k is not enough (not
doing so previously may rightfully be considered as a bug)
|
| | |
|
| | |
|