| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
this was an artifact from the original copy from omfwd. The options
were not functional and also not documented, so it is safe to simply
remove them.
|
|
|
|
| |
which lead the legacy config to be unusable.
|
| |
|
| |
|
|
|
|
|
|
| |
also max number of templates for plugin use has been increased to five
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=392
|
|
|
|
|
|
|
| |
It's still 5-6 seconds late and this happens also
in dmesg from util-linux.
modified: plugins/imkmsg/kmsg.c
|
| |
|
|
|
|
|
| |
... well, it's actually questionable if it is a real optimization
or not ;)
|
|
|
|
| |
modified: plugins/imjournal/imjournal.c
|
|
|
|
| |
modified: plugins/imjournal/imjournal.c
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Move the severity-check logic inside the ratelimiter and add a new
function ratelimitSetSeverity() to manipulate the treshold.
Currently only utilized by the imuxsock module.
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
runtime/queue.c
|
| | |
| | |
| | |
| | | |
it didn't do so if it was inside a retry loop
|
| | |
| | |
| | |
| | |
| | |
| | | |
... in more complex cases (where receiving SIGTTIN is not sufficient).
See also:
http://blog.gerhards.net/2013/04/rsyslog-output-plugin-wrangling.html
|
| | | |
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=409
Conflicts:
ChangeLog
|
| | |
| | |
| | |
| | | |
regression from ratelimiting enhancements
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
in that case, omlibdbi gracefully degrades to non-transaction mode
but emits a warning message during build, so that one knows an
update of libdbi makes sense.
|
| | | |
|
| | |
| | |
| | |
| | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=409
|
| | |
| | |
| | |
| | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=292
|
| | |
| | |
| | |
| | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=259
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previosly, this case could not be detected, so if a file was overwritten
or rotated away while rsyslog was stopped, some data was missing. This
is now detected and the new file being forwarded right from the
beginning.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=228
|
| |\| |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|