<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>----- 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>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>
<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>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>
<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>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>
</body>
</html>