Hi All, I've got a simple question on disk assisted queue behaviour, it could be trivial, but I can't find an answer on the internet.
I'm using rsyslog V5 to forward nginx access log to some logstash instances using omrelp Sometimes, because of activity burst, rsyslog flush onto disk 200 1Mo files (which is the expected behaviour), but then stays stuck, no more messages are sent to logstash. I have to delete state files as well as queue files so that rsyslog start sending messages to logstash again. Restarting rsyslog without deleting those files has no effect. Here is my rsyslog config in case I missed something $RuleSet nginxRuleSet $RulesetCreateMainQueue on $WorkDirectory /tmp $ActionQueueFileName queue-nginx $ActionQueueMaxDiskSpace 200m $ActionQueueSaveOnShutdown on $ActionQueueType LinkedList $ActionQueueSize 540000 $ActionResumeRetryCount -1 *.* :omrelp:<%= @lblog %>:5001;erableTmpl & ~ $InputUDPServerBindRuleset nginxRuleSet $UDPServerRun 515 Is it a known behaviour ? Thank you for any help one could provide Nicolas _______________________________________________ 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.
