| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| |
| | |
Conflicts:
tests/Makefile.am
tests/diag.sh
|
| | | |
|
| | |
| |
| |
| | |
The enhanced testbench now runs without failures, again
|
| | |
| |
| |
| |
| | |
also changed DA queue mode in that the regular workers now run
concurrently.
|
| | |
| |
| |
| |
| |
| | |
... in preparation for some larger changes - I need to apply some
serious design changes, as the current system does not play well
at all with ultra-reliable queues. Will do that in a totally new version.
|
| | |
| |
| |
| | |
slightly improved situation, would like to save it before carrying on
|
| | |
| |
| |
| |
| | |
... and now make check fails again, we have obviously found some new
bugs thanks to the additional cases
|
| |\|
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
tests/Makefile.am
tests/diskqueue.sh
tests/imtcp-multiport.sh
tests/manytcp.sh
tests/memq-persist.sh
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
The imdiag module now can very effectively inject messages, which also
frees us from uncertainties of tcp reception and processing. All shell
script based tests have been modularized, what makes it far easier to
create new tests. Also, the test bench now executes more reliable and
much faster, because we can now rely on actual engine information where
we previously did just a dumb sleep.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
... and also improved the test suite. There is a design issue in the
v3 queue engine that manifested to some serious problems with the new
processing mode. However, in v3 shutdown may take eternally if a queue
runs in DA mode, is configured to preserve data AND the action fails and
retries immediately. There is no cure available for v3, it would
require doing much of the work we have done on the new engine. The window
of exposure, as one might guess from the description, is very small. That
is probably the reason why we have not seen it in practice.
|
| | | |
|
| |\|
| |
| |
| |
| | |
Conflicts:
tests/Makefile.am
|
| | | |
|
| |\| |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
imdiag/imtcp had a modload race condition (as imdiag is a testing aid,
this has no implications for production deployments). Also, I replaced
netcat by a custom program to talk to imdiag. This, for the first time ever,
is now a Java program. I plan to add some GUI troubleshooting tools and
thought it is a good idea to start doing things in Java that can simply
be done in that language.
|
| |\|
| |
| |
| |
| |
| | |
Conflicts:
tests/Makefile.am
tests/diskqueue.sh
|
| | |
| |
| |
| |
| | |
which enables to talk to the rsyslog core at runtime. The current
implementation is only a beginning, but can be expanded over time
|
| | | |
|
| |\|
| |
| |
| |
| |
| |
| | |
Conflicts:
runtime/rsyslog.h
tests/Makefile.am
tools/syslogd.c
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Well, actually this and a lot of related things. I improved the
testbench so that the new capabilities are automatically tested and
also did some general cleanup. The current multiple tcp listener
solution will probably receive some further cleanup, too, but looks
quite OK so far. I also reviewed the way tcpsrv et all work, in
preparation of using this code for imdiag. I need to document the
findings, especially as the code is rather complicated "thanks" to
the combination of plain tcp and gssapi transport modes.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
... needed to split the old single counter into two. I wouldn't bet that
I made some mistakes while doing so, but at least some ad-hoc tests plus
the testbench do no longer indicate errors.
|
| |\|
| |
| |
| |
| | |
Conflicts:
tests/Makefile.am
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Only run omod-if-array.sh and parsertest.sh test if omstdout plugin is
enabled.
Remove the comment and fix the help output for --enable-stdout (default
was "no", not "yes")
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| |
| |
| |
| |
| | |
include <string.h> for memcpy and strlen.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| |
| |
| |
| |
| | |
... on the way to the ultra-reliable queue modes (redesign doc). This
version does not really work, but is a good commit point. Next comes
queue size calculation. DA mode does not yet work.
|
| | |
| |
| |
| | |
plus some cosmetic changes
|
| | | |
|
| | |
| |
| |
| | |
configuration directives
|
| | | |
|
| |/
|
|
|
|
|
|
| |
The problem is that the rsyslog engine writes messages too quickly, so
that the queue never enters DA mode. We still have some look contemption.
One possible solution (hopefully) is to finally move the parser code out
of imtcp and onto the next thread. Need to address these issues first, then
come back to the test case.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
as this send() option is not supported on Solaris. We now
simply ignore SIGPIPE
|
| |
|
|
| |
... to utilize it. This work is not yet fully verified to be correct.
|
| |
|
|
|
| |
Solaris network libraries needed to be specified
in linker options
|
| |
|
|
| |
... this time I think successfully (at least on Fedora...)
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
It is checked that many tcp connections are properly handled. While
adding this test, I noticed that there is a bug in imtcp that prevents
creation of more than 200 connections. This bug still exists, so the
test suite currently fails (what is correct). Will be addressed soon.
|
| |
|
|
|
| |
first noticed on FreeBSD
Also, some cosmetic improvements.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
- building the necessary plumbing to support more functions with
decent runtime performance. This is also necessary towards the
long-term goal of loadable library modules.
- added new RainerScript function "tolower"
|
| |
|
|
|
|
|
| |
We noticed this race issue under Solaris (thanks to its different
scheduler, I guess). In some cases, the previous instance of rsyslogd
was not terminated, resulting in a failure on the next test. Now
handled correctly.
|
| |
|
|
| |
new tests added, now much better
|
