Hi folks, jumping right in the middle and looking at one issue at the other ;)
Please note that nothing is silently ignored. Whenever rsyslog encounters a problem, a message is generated. HOWEVER, almost nobody ever looks at the messages emitted from the syslog facility and so the error messages are "lost". See also: http://blog.gerhards.net/2009/11/rsyslog-internal-messages.html For this, the $AbortOnUnleanConfig directive has been introduced, which will prevent rsyslog from starting if there is any problem. As the doc for that directive http://www.rsyslog.com/doc-rsconf1_abortonuncleanconfig.html says, enabling it can have harsh consequences. There is a reason that rsyslog by default does not abort - but rather emit an error message - and continue to function for that part of the config that is OK. This usually is much better than aborting. Please note that this is a long-term issue. For example, see this blog post: http://blog.gerhards.net/2008/07/rsyslog-error-reporting-how-to-do-it.html Since I have written this post, rsyslog now has a config check action and also emits error messages (if not disabled) to stderr during startup. I have to admit I have no further clue how I can make sure people actually look at the error messages... (it's quite frustrating for me). Any suggestions are very welcome. Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Mr. Demeanour > Sent: Friday, January 15, 2010 9:20 AM > To: rsyslog-users > Subject: Re: [rsyslog] rsyslog 5.3.6 (v5-beta) released > > [email protected] wrote: > > On Fri, 15 Jan 2010, Michael Biebl wrote: > > > >> 2010/1/15 Michael Biebl <[email protected]>: > >>> 2010/1/15 Philip M. Gollucci <[email protected]>: > >>>> Michael Biebl wrote: > >>>>>> ===== :programname, contains, "NetworkManager" > >>>>>> /var/log/NetworkManager.log ~ :programname, contains, > >>>>>> "wpa_supplicant" /var/log/NetworkManager.log ~ ===== > >>>> > >>>> 1) rsyslogd always pukes on itself if the config file doesn't > >>>> parse. not new. > >>>> > >>>> 2) Its documented that selectors syntax is not a stable API / > >>>> config file syntax, though, the maintainer should have noted it > >>>> in UPDATING. I would have hit this tomorrow myself. > >>>> > >>> > >>> You forgot the part, where I said that I remove those lines and > >>> rsyslog still doesn't log anything. > >> > >> And the fact that if it fails to parse, it should complain loudly > >> and not fail silently. > > > > unfortunantly in my experiance it doesn't complain loudly :-( > > > > in V5 there is a new option to tell it to exit if it can't read the > > config. > > Regarding failure to parse the config: > > If you have a config entry of this form: > > *.* -/var/log/syslog # Send everything else to syslog > > (i.e. with a trailing comment appended using hash), it doesn't work (on > 4.5.6, at least - I've observed this with other versions, but I don't > have a list). The config line is silently ignored. > > The manpage says: > "Lines starting with a hash mark ('#') and empty lines are > ignored." > > That's fair enough; but it doesn't mention that lines containing a > trailing comment will also be ignored (silently). > > Incorrect config lines should elicit a complaint in rsyslogd's output. > > -- > Jack. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
