Hello,
Here is a simple ruleset that I try to create:
ruleset(name="rs" queue.type="LinkedList" queue.filename="rsqueue") {
action(name="MainAction" type="omrelp" target="server1" port="514"
action.resumeRetryCount="0" action.resumeInterval="1")
action(name="BackupAction" type="omrelp" target="server2" port="514"
action.resumeRetryCount="0" action.resumeInterval="1"
action.ExecOnlyWhenPreviousIsSuspended="on")
}
*.* call rs
My problem is that in some situations the queueing, or at least the dequeing
does not appear to work.
For example, if server1 and 2 are not reached (perhaps because the senders
connection is disrupted) only the first 128 messages (I send a message every
second) after disconnection are queued. If the connection is re-established,
those are dequeued and sent to server1, and everything from there up to the
re-establishing of the connection is lost.
I try to show it graphically:
+++++++++|+++--------------------|+++++++
The | implicates the disconnection/reconnection of the network, + means
sent/queued, - means lost.
I had a look into the debug file, and when the connection is back, it shows
"now resending 128 unacked frames".
After 128 messages after disconnect it shows that the max windowsize has
been reached.
Is there something wrong with the ruleset queue? What do I need to change,
so that everything is queued and dequeued? Or is the solution to set the
windowsize to a really high number?
(It's version 8.1911.0)
--
Sent from: http://rsyslog-users.1305293.n2.nabble.com/
_______________________________________________
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.
