[syslog-ng] [Bug 46] Syslog-ng can go into and endless loop, consume all memory, and crash

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Mon May 4 10:35:53 CEST 2009


Balazs Scheidler <bazsi at balabit.hu> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #1 from Balazs Scheidler <bazsi at balabit.hu>  2009-05-04 10:35:53 ---
This is a positive feedback loop between the internal() source and one of the destinations (e.g. internal feeds messages to a given destination which in turn
generate error messages that originate from internal()).

There's a proper solution for this in syslog-ng 3.0, in which case it'll detect this case and drop internal messages accordingly.

Since the change is rather big, it cannot really be backported to either 2.0 or 2.1, so please use 3.0 if you want this fixed, or don't feed internal() 
logs to anywhere but a local static file, then read that file using the file() source. This is only a workaround I know.

I set this to WONTFIX on 2.0, a fix is available in later versions.

Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the syslog-ng mailing list