| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The original imjournal code did not support ratelimiting at all. We
now have our own ratelimiter. This can mitigate against journal
database corruption, when the journal re-sends old data. This is a
current bug in systemd journal, but we won't outrule this to happen
in the future again. So it is better to have a safeguard in place.
By default, we permit 20,000 messages witin 10 minutes. This may
be a bit restrictive, but given the risk potential it seems reasonable.
Users requiring larger traffic flows can always adjust the value.
|
| | |
|
| |
| |
| |
| |
| |
| | |
This prevents a segfault when a malformed journal entry field doesn't
contain an equal sign. Should not ever happen but was actually
triggered by a real bug in systemd journal.
|
|/
|
|
| |
if no problem happend at startup, everything went fine
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If the listen socket is opened earlier (during configuration parsing),
it is closed again during early init.
The start has been postponed to the 'runInput' stage, which has an
unpleasant side effect that it will fail if the priviledges are
dropped.
The code should be eventually fixed to support the new config system.
|
|
|
|
|
| |
sd_journal_wait() ignores EINTR and this behavior interferes with
module's termination signaling. Therefore, poll() is used instead.
|
|
|
|
|
| |
Because of cancelation, the correct possition in the journal was
lost. This resulted in duplicate messages appearing in the logs.
|
|
|
|
| |
modified: plugins/imjournal/imjournal.c
|
|
|
|
|
| |
This prevents linking with libee, liblognorm and libgcrypt when not
necessary.
|
|
|
|
|
| |
Through msg.h, many unrelated components needlessly required
LIBEE_CFLAGS.
|
| |
|
|
|
|
|
|
| |
When the imjournal state file path doesn't start with '/',
then it's by default stored in WorkDirectory. When path
starts with '/', full path is used.
|
| |
|
|
|
|
|
| |
This prevented state file from being written with newer systemd.
Add some more debug information.
|