We would need more information about exactly what is happening.
You have the watermark and discard severity values set, which means that when the queue gets too large it will throw some logs away.
Also, I'm not familiar with omazuremds, but it's possible that in some failure scenarios it's not detecting the failure soon enough, so it thinks that it's succeded when it really hasn't (this is how you can loose logs when forwarding over TCP, is spite of TCP being "reliable")
David Lang On Fri, 3 Oct 2014, Liwei Peng wrote:
Hi, In my new output plugin configuration file (see attached), I defined my action and queue to be able to resume forever. This was tested in its own conf and it worked well. However, when I included the conf into the overall rsyslog.conf, I found that some messages were not requeued, some were requeued. Can you tell me what's wrong with the configuration? Thanks. my module part which was tested and works: *.* action( type="omazuremds" template="fmt" mdsdport="29130" queue.workerthreads="1" queue.dequeuebatchsize="50" queue.type="fixedarray" queue.filename="mdsdqueue" queue.highwatermark="6000" queue.lowwatermark="1000" queue.discardseverity="8" queue.maxdiskspace="5g" queue.size="10000" queue.saveonshutdown="on" action.resumeretrycount="-1" action.resumeinterval = "3" )
_______________________________________________ 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.
