Hello, It smells like a bug because it shouldn't segfault. I think an issue on GitHub would help: https://github.com/rsyslog/rsyslog
Other than that, I think: - action queues are direct by default. You'd need to set queue.type to linkedlist or fixedarray first (to enable the memory part of the queue). You'd also need queue.filename to make a queue disk assisted. Or if you want a pure disk queue it would be queue.type=disk and queue.filename=/var/run/rsyslog/queue1 - I'm not sure if -1 disables the limit or 0 does. I would assume a large but realistic value would work better in production Best regards, Radu -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Sat, Aug 22, 2015 at 10:04 PM, rmkml <[email protected]> wrote: > Hi, > > First, Thx All for great rsyslog program ;) > > I have found a segfault on rsyslog v8.12 with simplified example : > > * then action(type="omfwd" queue.maxfilesize="-1" Target="127.0.0.1" > Port="10514" Protocol="tcp" ) > > and start rsyslog: > rsyslogd -f rsyslog.conf > Segmentation fault > > Anyone reproduce please ? > > Best Regards > @Rmkml > _______________________________________________ > 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. > _______________________________________________ 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.
