Indeed, it looks like the new functionality was not merged. Will check... Rainer
2014-09-27 14:36 GMT+02:00 Paul Freeman (Core Internet) < [email protected]>: > On 2014-09-27 13:29, David Lang wrote: > >> On Sat, 27 Sep 2014, Paul Freeman (Core Internet) wrote: >> >> The documentation at http://www.rsyslog.com/doc/v8- >>> stable/configuration/modules/ommail.html states: "Configuration >>> parameters are supported starting with v8.3.5. Earlier v7 and v8 versions >>> did only support legacy paramters." >>> >>> yet both 8.3.5 & 8.4.0 output the following error message: >>> >>> 8070.238340047:main Q:Reg/w0 : processBATCH: next msg 1: config objects >>> are not supported by module 'ommail' -- legacy config options MUST be used >>> instead [try http://www.rsyslog.com/e/ >>> 8070.238382305:main Q:Reg/w0 : rainerscript: var 1: 'config objects are >>> not supported by module 'ommail' -- legacy config options MUST be used >>> instead [try http://www.rsyslog.com/e/2210 ]' >>> >>> is there any version that actually supports new style config objects yet >>> ? >>> >> >> please post your config, you may just have an error in it >> > > > #module(load="immark") # provides --MARK-- message capability > module(load="imklog") # kernel logging (formerly provided by rklogd) > > # provides support for local system logging (e.g. via logger command) > module( > load="imuxsock" > SysSock.RateLimit.Interval="0" > ) > > module(load="ommysql") > module(load="imudp") # provides UDP syslog reception > module(load="imtcp") # provides TCP syslog reception > > module(load="ommail") > > > global( > workDirectory="/mnt/rsyslog-spool" > PreserveFQDN="on" > ) > > input(type="imudp" port="514") > input(type="imtcp" port="514") > > module( > load="builtin:omfile" > dirCreateMode="0770" > fileCreateMode="0670" > fileOwner="logmaster" > fileGroup="root" > dirOwner="logmaster" > dirGroup="root" > ) > > > template( > name="b2sys" > type="string" > string="/var/syslog/%HOSTNAME%/%$now%-Messages.log" > ) > > template( > name="mailBody" > type="string" > string="RSYSLOG Alert\r\nmsg='%msg%'" > ) > > template( > name="mailSubject" > type="string" > string="***WARNING*** Critical DISK I/O ERROR on %hostname%" > ) > > if $msg contains "end_request: I/O error, dev" then { > action( > type="ommail" server="mta2.mx.noc4.net" port="25" > mailfrom="rsyslog" > mailto=["[email protected]", "[email protected]"] > subject.template="mailSubject" > action.execonlyonceeveryinterval="30" > ) > } > > *.* action( > type="omfile" > DynaFile="b2sys" > queue.FileName="file-queue" > queue.MaxDiskSpace="8G" > queue.MaxFileSize="16M" > queue.SaveOnShutdown="on" > queue.Type="LinkedList" > action.ResumeRetryCount="-1" > > ) > > > > _______________________________________________ > 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.
