[syslog-ng] Syslog stops writing logs with extra [SQL] destination
koldaevav at gmail.com
Fri Oct 5 12:35:39 CEST 2012
I noticed it's not just sql logging related. If I've added any additional
destination to any existed log filters Syslog-ng stops writing logs to both
destinations after ~1min.
On Tue, Sep 18, 2012 at 1:28 PM, Anton Koldaev <koldaevav at gmail.com> wrote:
> I have the same "expr" logs going to file AND sql. With file-only logging
> it works great.
> When I'm enabling SQL logging it stops writing both to file and to sql
> ~1-10min(from 10 000 to 200 000 lines) after start.
> Every time there are no dropped messages, but 1000 stored for SQL location.
> syslog-ng 3.3.6
> - number of nodes: ~150
> - max-connections(200)
> - log_iw_size(20000)
> - log_fetch_limit(100)
> - log_fifo_size (400000);
> - flush_lines(100)
> - flush_timeout(100)
> - flags(flow-control) # the same issue with and without flow control
> syslog-server ~ % sudo syslog-ng-ctl stats | sort -rnk6 -t ";" | grep expr
> I see no errors in syslog-ng debug logs or mysql error log.
> After restarting syslog-ng it writes both logs for some time and stops
> I will appreciate any help.
> Additional question: is there any mysqltuner.pl-like tool for syslog-ng? I
> don't feel happy to tune all those buffers and windows manually with no
> being sure it will help.
> Best regards,
> Koldaev Anton
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the syslog-ng