<span style="font-family:arial,sans-serif;font-size:13px">> but you do see logging in the sql table for a while, then it stalls completely? that's interesting, and has no connection with window sizes, and seems to be a bug in sql. </span><br>
<div><span style="font-family:arial,sans-serif;font-size:13px">Yes I see logging in sql table for a while, then it stalls completely.</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">> </span><span style="font-family:arial,sans-serif;font-size:13px">like I said above, it doesn't seem to be window or tuning related. the sql driver stalls, which shoudln't happen if your sql server is available.</span><span style="font-family:arial,sans-serif;font-size:13px"> </span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">I'm able to write manually to my sql server when syslog-ng is already stalled. I've tried different mysql installations and it doesn't look like it the problem is on mysql side.</span></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 9, 2012 at 12:06 AM, Balazs Scheidler <span dir="ltr"><<a href="mailto:bazsi77@gmail.com" target="_blank">bazsi77@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
<p></p><div class="im">----- Original message -----
<br>> > this seems to be a bug in the sql destination. 1000 seems to be the
<br>> window size for your source, the queue becomes filled, but then the sql
<br>> destination doesn't flush messages.
<br>> > or does it?
<br>> Looks like it doesn't write anything after filling up to 1000. I spent a
<br>> few hours on waiting for it to be flushed but got no results.
<br>> log_iw_size for my source should be 20000:
<br>>
<br>> syslog(ip(0.0.0.0) transport("tcp") port(5141)
<br>> max-connections(200) log_iw_size(20000) flags("threaded")
<br>> log_fetch_limit(100));
<br>>
<br>
<br></div>syslog driver divides the log-iw-size() evenly accross all permitted connections (max-connections() option), that way you get a window size of 100 for each connection.
<br><div class="im">
<br>>
<br>>
<br>> > it might also happen that it's slow. syslog-ng maxes out the queue,
<br>> > then
<br>> stops until messages are emptied. once there are free slots it starts
<br>> again: fills it up, stalls.
<br>> Looks like it never gets any free slots in my configuration since I don't
<br>> see any logging after the queue is maxed out for a few hours.
<br>>
<br>
<br></div>but you do see logging in the sql table for a while, then it stalls completely? that's interesting, and has no connection with window sizes, and seems to be a bug in sql.
<br><div class="im">
<br>> Could you give me any recommendations? Looks like log_iw_size just
<br>> doesn't work for my source and I have no idea how to fix it.
<br>>
<br>
<br></div>like I said above, it doesn't seem to be window or tuning related. the sql driver stalls, which shoudln't happen if your sql server is available.
<br>
<br>Algernon, can you have a look? I don't when I can get there :(<p></p>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Best regards,<br>Koldaev Anton<br>
</div>