Hi, On Tue, Feb 3, 2015 at 4:13 AM, Rainer Gerhards <[email protected]> wrote:
> 2015-02-03 0:30 GMT+01:00 David Lang <[email protected]>: > > > > > On Mon, 2 Feb 2015, Otis Gospodnetic wrote: > > > > Hi, > >> > >> Just installed the very latest 8.7.0 on one machine and spotted this in > >> the > >> log: > >> > >> Feb 2 23:24:27 logsene-reports rsyslogd-2207: error during parsing file > >> /etc/rsyslog.conf, on or before line 55: warnings occured in file > >> '/etc/rsyslog.conf' around line 55 [try http://www.rsyslog.com/e/2207 ] > >> > >> > >> > didn't you get the other error message? This is what I see: > > 2015-02-03T10:10:14.076337+01:00 ubuntu1404esp rsyslogd-2184: action '*' > treated as ':omusrmsg:*' - please change syntax, '*' will not be supported > in the future [v8.8.0.master try http://www.rsyslog.com/e/2184 ] > 2015-02-03T10:10:14.146723+01:00 ubuntu1404esp rsyslogd-2207: error during > parsing file bluecoat.conf, on or before line 7: warnings occured in file > '/bluecoat.conf' around line 7 [v8.8.0.master try > http://www.rsyslog.com/e/2207 ] > I did see this. I didn't know how to interpret it. May I change a slight change in wording? A bit more direct for people less familiar with (r)syslog-specifics? e.g. action '*' treated as ':omusrmsg:*' - please change syntax, '*' will not be supported in the future vs. action '*' treated as ':omusrmsg:*' - please use ":omusrmsg:" syntax instead, '*' will not be supported in the future This is a bit more direct and informative IMHO. It's not telling me just that there is a problem - it's telling me what to do to fix it. Otis -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr & Elasticsearch Support * http://sematext.com/ > > Rainer > > Looking at line 55, it's this: > >> # Everybody gets emergency messages > >> *.emerg * > >> > >> If I comment it out, the warning goes away. Some legacy thing I should > >> remove from rsyslog.conf? > >> > > > > What it is supposed to do is that an emergancy priority message would be > > shown to everyone that's logged in to the system. > > > > The fact that this gives a parsing error is a bug in rsyslog. > > > > But I don't think you will miss this if you just comment it out. > > > > Daivd Lang > > > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com/professional-services/ > > What's up with rsyslog? Follow https://twitter.com/rgerhards > > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > > DON'T LIKE THAT. > > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
