Hi Thomas, these are the steps to reproduce the issue:
- set up a RHEL 7 enviroment - install rsyslog v8.10.0 from release tarball with this configure statement: ./configure --prefix=/usr --enable-gnutls --enable-mysql - load ommysql module and create a write to database action in your configuration This should produce the error message directly at the startup. I recommend you to write everything into a logfile where you can find the error message. Simply add this to your configuration to produce the error: *.* /var/log/all-messages.log $ModLoad ommysql $ActionOmmysqlServerPort 1234 # use non-standard port *.* :ommysql:mysqlserver.example.com,syslog_db,user,pwd How do you verify the problem? If rsyslog produce the error message: rsyslogd-2007: can not initialize MySQL handle [v8.10.0 try http://www.rsyslog.com/e/2007 ]. rsyslog will not write into the database then. So if you use my config example then you should receive the error that rsyslog can't connect to the database and not the error message "can not initialize MySQL handle.." if the problem doesn't occurs. Greetings, Tim 2015-06-10 14:24 GMT+02:00 Thomas D. <[email protected]>: > Hi, > > Rainer Gerhards wrote: > > Just for the records: you can't hold back the v8.11 tarball because it > > will be released roughly in the future > > You catched me time traveling ;-) > > > > We finished the bisect. This is the commit in questions: > > > > > https://github.com/rsyslog/rsyslog/commit/23c5b3e1e62ee2daf5cce61c7e80f5e20898c03b > > > > I replaced deprecated GnuTLS functions with that commit. I do not see > > any direct relation to why it makes ommysql fail if compiled from > > tarball, but there obviously is some. The problem goes away if during > > configure we --disable-gnutls and reapears reproducible when doing > > --enable-gnutls. > > > > If I remove the two lines added to configure.ac with that commit, > > ommysql works well. The strange thing is that GnuTLS does not even > > need to be used in an config to make the issue appear. It's sufficient > > if the option is enabled. > > > > It looks like for now I'll revert to using the deprecated GnuTLS > > functions. But that's for sure not a solution for eternity... > > > > Does anone have a clue what this could be? Do I overlook some > > autotools automagic? > > I have an idea but before I a make a fool of myself: What's needed to > reproduce the problem (or how do you verify the problem is gone)? > > Build from a source with this commit and just set up rsyslog to write > logs into mysql using ommysql? So I should see an error on rsyslog > startup like Tim quoted or when an action calls ommysql? > > Do I need anything else? > > Was mysqlconfig.* used? A DSN with TLS? > > > -Thomas > > _______________________________________________ > 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.
