On Fri, 11 Dec 2009, Kenneth Marshall wrote: > On Fri, Dec 11, 2009 at 01:04:25PM +0100, Rainer Gerhards wrote: >> if not subscribed to it, revisit bug tracker or forum post, there now exist a >> patch! :) >> >> Rainer >> > Thank you Rainer. It now logs once more. Unfortunately, I am having > trouble getting the INSERT batching to work. Here is my current > rsyslog.conf:
note that rsyslog will only batch if it falls behind. the output module basicly does a tight loop: any messages to process? yes, grab up to batch size of them, process them and repeat. if there is only one message in the queue it will process that and loop back. David Lang > $ModLoad immark # provides --MARK-- message capability > $ModLoad imtcp # provides TCP syslog reception and GSS-API (if compiled to > support it) > $ModLoad imuxsock > $InputTCPServerRun 601 # listen on this port > $WorkDirectory /var/spool/rsyslog # default location for work (spool) files > #$MainMsgQueueFileName mainq # set file name, also enables disk mode > $ActionQueueType LinkedList # use asynchronous processing > $ActionQueueDequeueBatchSize 16 > $ActionQueueFileName dbq # set file name, also enables disk mode > $ActionResumeRetryCount -1 # infinite retries on insert failure > $ModLoad ompgsql # provides postgres support > # Everything we receive goes in the database > *.* :ompgsql:127.0.0.1,Syslog,dbuser,xxxxxx > > The $ActionQueueDequeueBatchSize option does not appear to have > any effect. The inserts are still performed one at a time. Any > ideas? > > Regards, > Ken > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
