[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
Tue May 5 14:50:20 CEST 2009


--- Comment #2 from Sikkerhed.org ApS <support at sikkerhed.org>  2009-05-05 14:50:20 ---
(In reply to comment #1)
> 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.

Ok. We've rolled out syslog-ng on all our servers now anyway, so it shouldn't be a problem from here on.

It was, however, a little unnerving when it first happened, before I figured out why :-)

Are there other major reasons to use version 3.x over 2.x? 

By the way, there's a problem with your mail server configuration. When replying to a bug report, it says:

<bugzilla at bugzilla.balabit.com>: host bugzilla.balabit.com[] said:
    554 5.1.1 <bugzilla at bugzilla.balabit.com>: Recipient address rejected:
    undeliverable address: mail for bugzilla.balabit.com loops back to myself
    (in reply to RCPT TO command)

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