Bug 237887 - syslog-ng not tolerant of configuration errors
syslog-ng not tolerant of configuration errors
Product: Fedora
Classification: Fedora
Component: syslog-ng (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Douglas E. Warner
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-04-25 17:11 EDT by Steve Friedman
Modified: 2008-02-22 23:12 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-02-22 23:12:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Steve Friedman 2007-04-25 17:11:42 EDT
Description of problem:

Syslog-ng is not tolerant of configuration errors -- rather than start those
elements that are valid, it will not start at all.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Configure syslog-ng with a partially invalid configuration (see below for
some examples).
2. /etc/init.d/syslog-ng start
Actual results:
Syslog-ng will fail to start, generating an explanation of the problem.

Expected results:
Syslog-ng should start those destinations / sources / filters that are valid. 
It should still generate an explanation of what wasn't started, but valid
elements should live.

Additional info:
Examples of invalid configurations include:

- destination bogus   { udp( "dest_addr" localip(non-existent-addr) port(8913) 
); };
  In this case, as syslog-ng can't bind to non-existent-addr, only this
destination should be disabled (rather than the entire logging system).

- log { source(s_sys);  destination(non-existent); }
  Again, the non-existent destination should disable this one log element, not
the entire logging system.
Comment 1 Douglas E. Warner 2008-02-22 23:12:25 EST
syslog-ng doesn't support silently ignoring config options.  Their desired 
behavior for upstream is to error out when configured options won't work.

Note You need to log in before you can comment on or make changes to this bug.