8 May
2013
8 May
'13
7:13 p.m.
On 05/07/2013 09:41 PM, Balazs Scheidler wrote:
Now as I think of it If you are really using 3.2 another issue may be the cause, is there another client that sends a lot of traffic parallel to logger? One source may starve the other. That's why the window allocation was changed.
In any case try to increase that and see if it helps.
No, there isn't any other source sending to the syslog-ng receiver. I will try to tweak the window allocation nevertheless and see if it helps. Will update list with the resolution. Thanks!