Re: [rsyslog] RES: Client/server architecture with omrelp/imrelp - Lost of messages in case of server side failure

2017-10-30 Thread mostolog--- via rsyslog
Hi You are missing retryInterval, and I would say it's needed for proper retry after a queue lock. In our tests, once relp queue was full, it never resumed (although resumeretrycount=-1 was set) until we added interval setting. On 26/10/17 15:52, Jether B. Santos via rsyslog wrote: Hi,

[rsyslog] RES: Client/server architecture with omrelp/imrelp - Lost of messages in case of server side failure

2017-10-26 Thread Jether B. Santos via rsyslog
Hi, In order to not loose any message I realized I have to change the queue.dequeuebatchsize to "1" and action.resumeretrycount to a value greater than default "0" (I used "-1" for infinite). That configuration has worked for me: ruleset(name="remote_logserver"){ action(type="omrelp"

[rsyslog] RES: Client/server architecture with omrelp/imrelp - Lost of messages in case of server side failure

2017-10-23 Thread Jether B. Santos via rsyslog
Hello, I realized the parameter RebindInterval was causing duplicated messages in both balanced servers. I removed that and apparentely the messages haven't been lost anymore. Tomorrow I will stress it more. Regards, Jether De: Jether B. Santos Enviada em: segunda-feira, 23 de outubro de 201