| 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
|
| |
|
|
| |
most importantly, convert sample to new-style config format
|
| |
|
|
|
| |
... was changed in the interim, so the result of the merge was
sub-optimal ;)
|
| |\
| |
| |
| |
| | |
Conflicts:
plugins/imjournal/imjournal.c
|
| | |
| |
| |
| |
| | |
modified: doc/imjournal.html
modified: plugins/imjournal/imjournal.c
|
| | |
| |
| |
| | |
thanks to David Lang for alerting me.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| | |
do to bugs in systemd, the module can lead to a DoS to the local machine
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There is a time window, between rsyslog reporting syntax
errors and the daemon returning with failure, this may cause
systemctl restart rsyslog to not report any error inmediately
but later in the logs which is confusing to users.
The appropiate steps to correct this annoyance is to notify
systemd with a simple sd_notify(0, "READY=1"); just before
entering the main loop.
Tested in openSUSE 12.3/13.1 x86_64
|
| | |
| |
| |
| |
| |
| | |
Those are documented here:
http://www.freedesktop.org/wiki/Software/systemd/syslog/
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
The message that reports how many messages were lost due to
ratelimiting was sent before reseting the state that led to it. If it
itself got ratelimited, this could lead to an endless loop.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
If messages are being dropped because of ratelimiting, an internal
message is generated to inform about this fact. This should happen
only uppon the firs occurance but the counter that tracks the number
of dropped messages was incremented only after sending the message. If
the message itself gets ratelimited, an endless loop spins out of
control. Thanks to Jerry James for notifying about this.
|
| | |
| |
| |
| |
| |
| | |
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
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Some of the options affect all files, not just dynafiles.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If multiple spaces were used in front of the template name, all but one
of them became actually part of the template name. So
$template a,"..." would be name " a", and as such "a" was not
available, e.g. in
*.* /var/log/file;a
This is a legacy config problem. As it was unreported for many years,
no backport of the fix to old versions will happen.
This is a long-standing bug that was only recently reported by forum
user mc-sim.
Reference: http://kb.monitorware.com/post23448.html
|
| |
|
|
|
| |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=450
Thanks to jokajak@gmail.com for mentioning this
|
| |
|
|
|
|
|
| |
permits to build rsyslog on a system where rst2man is not installed. In
that case, cached versions of the man pages are used (they were built
during "make dist", so they should be current for the version in
question.
|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
This reverts commit 813c9c7f524976ef598864afbb729bca31557c32.
Removing references to libee.h in the previous commit solves the build
issue so the cflag shoudn't be needed after all.
|
| |
|
|
|
| |
Through msg.h, many unrelated components needlessly required
LIBEE_CFLAGS.
|
| | |
|
| |
|
|
|
|
| |
The macro itself was a malformed version of "_GNU_SOURCE" and thus had
no effect. It is not needed as this macro is already defined
via AC_GNU_SOURCE.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
| |
Thanks to Tomas Heinrich and winfried_mb2@xmsnet.nl for the patch.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=445
|
| | |
|
| |
|
|
| |
Called when either libgcrypt or GuardTime is enabled.
|
| | |
|
| | |
|
| |
|
|
|
| |
This prevented state file from being written with newer systemd.
Add some more debug information.
|
