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.
