[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"

Re: [rsyslog] Truncated UDP message error is shown on debug?

2017-10-26 Thread Rainer Gerhards
2017-10-26 9:08 GMT+02:00 mostolog--- via rsyslog : > Hi > > As we were not receiving messages from one server while doing some tests, we > run: > rsyslogd -dn > but we weren't able to see anything wrong. > > However, running: > rsyslog -n > showed the following message: > rsyslogd: omf

[rsyslog] Truncated UDP message error is shown on debug?

2017-10-26 Thread mostolog--- via rsyslog
Hi As we were not receiving messages from one server while doing some tests, we run:     rsyslogd -dn but we weren't able to see anything wrong. However, running:     rsyslog -n showed the following message:     rsyslogd: omfwd/udp: message is 113152 bytes long, but UDP can send at most 65507