On Tue, 14 Feb 2017, mostolog--- via rsyslog wrote:
While using RELP to forward messages to a central rsyslog, we had a full disk
issue on target.
After cleaning the disk and recovering space, relay rsyslog seems is not
forwarding traffic as it should (full speed!).
Messages with priority 12 still arrive, and impstats shows:
Feb 14 11:22:21 relay rsyslogd-pstats: fwdtocentral: origin=core.queue
size=900000 enqueued=107845543 full=0 discarded.full=0 discarded.nf=41435274
maxqsize=90138
Could it be suspendDuration went too high after 2 days with high
traffic(60k/min)?
possible
Is there any way to query suspendDuration value while running? (without
DEBUG!)
there is a setting to have it log suspend messages, that gives you the duration.
It's something that goes in the main() section. I'd have to dig to find it
though.
Does it suspendDuration gets decreased when connection is recovered? (I won't
say that after reading action.c)
Shall suspendDuration have a maximum value?
if it doesn't, it should
Will HUP signal reset suspendDuration and start forwarding normally?
I believe so, because the HUP will close all outputs and restart them on the
next message
Is there anything I could test to help fixing this (if it's a bug)?
just a note, you can define the debug file in the config and then turn debug on
and off while running, no overhead when it's off.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
