https://bugzilla.balabit.com/show_bug.cgi?id=208 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED --- Comment #18 from Gergely Nagy <algernon@balabit.hu> 2013-01-15 12:18:53 --- (In reply to comment #15)
(In reply to comment #14)
Unfortunately I'm seeing almost the same problem even with updated version(3.3.7). Looks like I'm not able to reproduce it this time on my test server but in production I see syslog-ng consumes all the memory again.
Mhhmm. I can reproduce it too, but I won't have time to investigate further for a few days. In the meanwhile, I'd suggest pulling out the internal() source into its own source, and add it to a logpath that does not go through filters. That should work around the issue until we can fix it properly.
I haven't been able to reproduce it since (only once, but then a few days later, I couldn't make it OOM again :/), but I'll give it another go tomorrow. Are you still experiencing the issue with current 3.3 git master? -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.