2010/1/15 Michael Biebl <[email protected]>: > 2010/1/13 Rainer Gerhards <[email protected]>: >> Hi all, >> >> I have just released rsyslog 5.3.6, a new v5-beta. Note that this version >> contains a number of bug fixes, some of them important for some environments. >> As usual for a beta, it does not contain anything else but fixes. The full >> lest can be seen in the change log. >> >> Please note that it is my intent do replace the current (instable ;)) >> v5-stable by this beta soon. So I would appreciate feedback on 5.3.6 - if I >> get a few thumbs up, I may be able to accelerate promoting it to stable. > > So I gave 5.3.6 a try and stumbled over some rather important regressions. > > Compilation and installation went fine and rsyslog started up without > an error message. > I got one log message in the syslog > Jan 15 07:39:29 pluto kernel: imklog 5.3.6, log source = /proc/kmsg started. > > But silence afterwards. > > When I tried to stop rsyslog using SIGTERM it failed, I had to use SIGTERM > twice > > Running rsyslogd -d -c4 I got > pluto:~# rsyslogd -d -c4 > rsyslogd: unknown priority name "" [try http://www.rsyslog.com/e/3000 ] > rsyslogd: the last error occured in > /etc/rsyslog.d/network-manager.conf, line 2:"~" > rsyslogd: warning: selector line without actions will be discarded > rsyslogd: unknown priority name "" [try http://www.rsyslog.com/e/3000 ] > rsyslogd: the last error occured in > /etc/rsyslog.d/network-manager.conf, line 4:"~" > rsyslogd: warning: selector line without actions will be discarded > rsyslogd: the last error occured in /etc/rsyslog.conf, line > 46:"$IncludeConfig /etc/rsyslog.d/*.conf" > rsyslogd: CONFIG ERROR: could not interpret master config file > '/etc/rsyslog.conf'. [try http://www.rsyslog.com/e/2124 ] > > The file in question (which worked fine with 4.4.2) contains > ===== > :programname, contains, "NetworkManager" /var/log/NetworkManager.log > ~ > :programname, contains, "wpa_supplicant" /var/log/NetworkManager.log > ~ > ===== > > > several issues here: > first of all, the above statements no longer work. > second, rsyslog can't be killed anymore with a single SIGTERM > third, it shouldn't just silently fail. I neither got an error message > on stdout/stderr, nor in the log file.
fwiw, changing -c4 to -c5 and removing network-manager.conf didn't help. rsyslog still logs nothing and rsyslog -d is suspicously silent (i.e. no output). Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
