Hi Bill, Lucky shot attempt no1 :D
Regarding these: $ModLoad imtcp.so $ModLoad imtcp.so Are you sure it doesn't try to load the modules for v5? When in doubt, provide the full path to the libraries you compiled for v7.2.1. Or even better, try removing them from the config and see if it starts. Then you'd have some new info. 2012/11/15 Bill Burge <[email protected]> > Rsyslog won't start. > > #### It throws the following error: > > Starting system logger: rsyslogd: error: option -c is no longer supported > - ignored > rsyslogd: run failed with error -2207 (see rsyslog.h or try > http://www.rsyslog.com/e/2207 to learn what that number means) > [FAILED] > > #### And this is our original rsyslong.conf from the old server: > > $ModLoad imtcp.so > $ModLoad imtcp.so > $UDPServerRun 514 > $InputTCPServerRun 514 > $template RawFormat,"%msg:3:$%\n" > $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat > $EscapeControlCharactersOnReceive off > > > #$AllowedSender UDP, 0.0.0.0/0 > #$AllowedSender TCP, 0.0.0.0/0 > $umask 0222 > > # The authpriv file has restricted access. > $template DynAuth, "/var/log/remote/%HOSTNAME%/secure.log" > > # Log anything (except mail and cron) of level info or higher. > $template Dynstuff, "/var/log/remote/%HOSTNAME%/messages" > > # Log all the mail messages in one place. > $template Dynmail, "/var/log/remote/%HOSTNAME%/maillog" > > # Log cron stuff > $template Dyncron, "/var/log/remote/%HOSTNAME%/cron" > > # Save news errors of level crit and higher in a special file. > $template Dynspool, "/var/log/remote/%HOSTNAME%/spooler" > > # Save boot messages also to boot.log > $template Dynboot, "/var/log/remote/%HOSTNAME%/boot.log" > > # Save IIS weblogs into a weblog file > $template Dynweb, "/var/log/remote/%HOSTNAME%/IIS/%SYSLOGTAG%.log" > > # Save WebSphere weblogs into a weblog file > $template Dynwas, "/var/log/remote/%HOSTNAME%/WAS/%SYSLOGTAG%.log" > > # Save Other Java weblogs into a weblog file > $template Dynjava, "/var/log/remote/%HOSTNAME%/JAVA/%SYSLOGTAG%.log" > > # Save Generic logs into a file > $template Dynallogs, > "/var/log/remote/%HOSTNAME%/%SYSLOGTAG%/%SYSLOGTAG%.log" > > # Application Event logs > $template Dynapp, "/var/log/remote/%HOSTNAME%/application.log" > > # Security Event logs > $template Dynsec, "/var/log/remote/%HOSTNAME%/security.log" > > # System Event logs > $template Dynsys, "/var/log/remote/%HOSTNAME%/system.log" > > #Activate the templates > authpriv.* ?DynAuth > #mail.none,authpriv.none,cron.none ?Dynstuff > mail.none, news.none, authpriv.none, cron.none ?Dynstuff > mail.* -?Dynmail > cron.* ?Dyncron > news.crit ?Dynspool > local7.* ?Dynboot > local0.* ?Dynweb;RawFormat > local5.* ?Dynwas;RawFormat > local6.* ?Dynjava;RawFormat > local1.* ?Dynallogs > local2.* ?Dynapp > local3.* ?Dynsec > local4.* ?Dynsys > > ----- > Bill Burge > Brown Shoe Company, Inc. > 314.246.0328 tel > > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Rainer Gerhards > Sent: Thursday, November 15, 2012 3:10 PM > To: [email protected] > Subject: Re: [rsyslog] rsyslog.conf for 7.2.1 > > which issues do you see? the old conf should work. > > > Sent from phone, thus brief. > > Bill Burge <[email protected]> hat geschrieben: > I've sort of been thrown into resolving issues we have with a rsyslog 3.x > implementation on CentOS. I have rebuilt a RHEL 6.3 server with 7.2.1 > installed. Our existing rsylong.conf obviously won't cut it because of > some compatibility issues, and the included rsyslong.conf in the rpm > package was for 5 and also won't start. > > I see examples on the rsyslog site that also seem quite old so I'm > wondering if anyone can point me towards a baseline configuration to start > from? We ultimately will be forwarding IIS logs to the server with > Adiscon's MonitorWare package. > > ----- > Bill Burge > Brown Shoe Company, Inc. > 314.246.0328 tel > _______________________________________________ > 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. > _______________________________________________ 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.
