| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
Conflicts:
ChangeLog
|
| |
|
|
| |
This is now properly handled inside rsyslog core.
|
| |
|
|
| |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=448
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
imdiag may not have enough time to properly terminate when the
shutdown request is made. Thus we give it a little headroom. Note
that this does not address a real issue inside the code - at most,
it looks like a memory leak, but one where the whole process is
immediately destructed. However, it is an annouance for the testbench.
Note that the race may still occur based on circumstances, but now
is much less likely.
|
| |
|
|
|
| |
do --enable-valgrind to get better diagnostics in case of
memory leaks
|
| |
|
|
|
| |
The last fix was incomplete. Thanks to Christiano for testing
and suggestions.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=456
|
| |
|
|
| |
this clould result to segfaults on startup if parameters were missing.
|
| | |
|
| | |
|
| |
|
|
| |
Thanks to Christiano for reporting this problem.
|
| |
|
|
| |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=458
|
| | |
|
| | |
|
| |
|
|
|
| |
Fixes
./configure: line 18474: xno: command not found
|
| | |
|
| |
|
|
|
| |
always bears the risk that one or another is not maintained when
an update happpens
|
| | |
|
| |
|
|
|
| |
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
|
| |
|
|
| |
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.
|
