On Wed, Jul 4, 2012 at 5:58 PM, Evan Rempel <erempel@uvic.ca> wrote:

So upgrading from 2.x to 3.x (there may be other cases) and not removing that file will yield the
result you are seeing.

Thanks for the idea, but that's not the case. It's a fresh install with syslog-ng 3.2.4 since the beginning. Moreover, it seems it's working correctly for log files that receive less traffic.