The behavior of ommongodb was for a long time to abort on MongoDB insertion error; keeping this behavior, I wanted to add the possibility to ignore some error code that may be allowed in some configuration (ex. 11000 DuplicateKey in case of collection containing a unique filed).
The directive arguments MUST be in the following format (handling a maximum of 256 codes): "11000,...,17,64"
This makes the ES tests more universally available (they should now
also support running in containers). It also simplifies the tests
as fewer support files are needed.
Commit 7589f42e45888b83f5c2a0d788896d41e6a6a598 introduced support
for loading certificate chains. Unfortunatley the max number of permitted
certificates was miscalculated and so a certificate chain with more than
10 certificates could lead to a buffer overrun. This patch corrects this.
Note that the commit was merged just yesterday and there was no release
with the affected code.
Also, this commit adds GNUTLS_X509_CRT_LIST_IMPORT_FAIL_IF_EXCEED to
ensure the certificate export will fail with an error message if the
certificate list contains too many certificates. Thx to Arne Nordmark
for suggesting that option.
Add support for a 'create' write operation type in addition to
the default 'index'. Using create allows specifying a unique id
for each record, and allows duplicate document detection.
Add support for checking each record returned in a bulk index
request response. Allow specifying a ruleset to send each failed
record to. Add a local variable `omes` which contains the
information in the error response, so that users can control how
to handle responses e.g. retry, or send to an error file.
Add support for response stats - count successes, duplicates, and
different types of failures.
Add testing for bulk index rejections.
Triggering condition:
- action queue in disk mode (or DA)
- batch is being processed by failed action in retry mode
- rsyslog is shut down without resuming action
In these cases messages may be lost by not properly writing them
back to the disk queue.
closes https://github.com/rsyslog/rsyslog/issues/2760
Added them after intensive checking that these are indeed false positives.
Among other, checks via TSAN as well as intensive manual debugging of that
issue. Also, no other platform shows the issues. So I conclude that it is
safe to suppress it.
