| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Thanks to Tomas Heinrich for alerting us and provinding a solution
suggestion.
|
|
|
|
|
|
|
| |
Not doing so caused that the system log socket was unaffected by these
directives.
bCreatePath is still not passed but currently, there's no placeholder for it.
|
| |
|
|
|
|
|
|
|
| |
This could cause message loss on systems under heavy load and was
a change-of-behaviour to previous version. This is a regression
most probably introduced in 5.9.0 (but did not try hard to find the
exact point of its introduction).
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This usually did not lead to any problems, because they are in static
memory, which is initialized to zero by the OS when the plugin is
loaded. But it may cause problems especially on systems that do not
support atomic instructions - in this case the associated mutexes also
did not get properly initialized.
|
| |
|
| |
|
|
|
|
|
|
|
| |
The problem occured if two IPs were close to each other and the first one
was shrunk.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=485
Thanks to micah-at-riseup.net for reporting this bug
|
|
|
|
|
|
|
|
| |
depending on configuration sequence, the replacement character was set
to 's' instead of the correct value. Most importantly, it was set to
's' if simple mode was selected and no replacement char set.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=484
Thanks to micah-at-riseup.net for reporting this bug
|
| |
|
|
|
|
|
|
|
|
| |
As it turned out, this didn't work in practice as there
was an enormous set of potential terminator chars -- so removing
them was the best thing to do. Note that this may change behaviour of
existing installations. Yet, we still consider this an important
bugfix, that should be applied to the stable branch.
|
|
|
|
|
|
| |
This is used in Exim and Postfix ... and probably a bunch of other tools
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=477
Thanks to Muri Cicanor for requesting the addition
|
|
|
|
| |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|
|
|
|
|
| |
caused facility not to be set, and severity to be overwritten with
the facility value.
Thanks to forum user dmunny for reporting this bug.
|
|
|
|
| |
Thanks to Grégory Nuyttens for reporting this bug and providig a fix
|
|
|
|
|
|
| |
Conflicts:
plugins/omelasticsearch/omelasticsearch.c
|
|
|
|
| |
Thanks to Michael Biebl for mentioning the problem.
|
|
|
|
| |
The faulty code was never released.
|
| |
|
|
|
|
|
| |
due to a case typo in imfile; work-around was to use legacy config
Thanks to Brandon Murphy for reporting this bug.
|
|
|
|
| |
Thanks to Chris Norton for alerting us.
|
| |
|
|
|
|
| |
If there was no default template, a segfault occured on startup.
|
|
|
|
|
| |
Using OMSRsetEntry now to set the default action template when using new-style config.
See here for more: http://bugzilla.adiscon.com/show_bug.cgi?id=468
|
|
|
|
|
| |
See http://bugzilla.adiscon.com/show_bug.cgi?id=468
Removed CNFPARAM_REQUIRED from all optional parameters.
|
|
|
|
|
|
| |
Added check for empty batch data in endTransaction function.
Avoids sending an unneeded curlPost, can happen when elasticsearch is shutdown
while sending data to.
|
|
|
|
|
|
| |
http://bugzilla.adiscon.com/show_bug.cgi?id=464
A Check was added for replylen before writting the 0 Byte to the end of reply data.
|
|
|
|
|
|
| |
Added some libcurl options in checkConn to disable the bodyport of the
request within this functions. Otherwise libcurl could have created a
sigsegv when curl_easy_perform() was called.
|
|
|
|
|
| |
This happened to errors occuring in Begin/End Transaction entry
points.
|
| |
|
| |
|
|
|
|
|
| |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=461
Thanks to Marius Ionescu for providing a detailled bug report
|
|
|
|
|
| |
Conflicts:
ChangeLog
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=456
|
|
|
|
| |
this clould result to segfaults on startup if parameters were missing.
|
| |
|
|
|
|
| |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=458
|
|
|
|
|
| |
Too quick hacking, obviously, one too late, one too early, now
it should fit ;) Thanks to Tomas Heinrich for pointing this out.
|
|
|
|
| |
No regression, this was in recently written, never-released code.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and make imjournal use it.
The new mode is needed, as imjournal uses journal's timestamp
as message generation time (which otherwise is when the message
entered the system, and the ratelimiter uses this as current
timestamp in order to save performance).
It is debatable if imjournal is doing the right thing here. But
it doesn't feel totally wrong. So let's safe that debate for
later ;)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This option specifies whether imjournal should ignore messages
that are currently in journal. This option is only used when there
is no StateFile to avoid message loss.
modified: doc/imjournal.html
modified: plugins/imjournal/imjournal.c
Conflicts:
doc/imjournal.html
plugins/imjournal/imjournal.c
|
|\
| |
| |
| |
| | |
Conflicts:
plugins/imjournal/imjournal.c
|
| |
| |
| |
| |
| | |
modified: doc/imjournal.html
modified: plugins/imjournal/imjournal.c
|