Update: I've installed GnuTLS manually (3.1.18, the latest version) and I'm getting the same error. I'm still trying to figure out what to do here.
In the meantime, Google found this: https://github.com/PromyLOPh/pianobar/issues/182 Maybe it helps if it's possible to have im/omrelp work with gnutls <=2.10 ? Best regards, Radu 2014/1/14 Radu Gheorghe <[email protected]> > Hi list! :) > > I have a question. It looks like this guy is not the only one: > > http://kb.monitorware.com/usr-lib64-librelp-undefined-symbol-gnutls-certificat-t12109.html > > I've just updated to CentOS 6.5 and I still have gnutls 2.8.5 installed, > so imrelp from the official RPM packages doesn't load: > --------- > rsyslogd: could not load module '/lib64/rsyslog/imrelp.so', dlopen: > /usr/lib64/librelp.so.0: undefined symbol: > gnutls_certificate_set_verify_function [try http://www.rsyslog.com/e/2066] > --------- > > Luckily we have RPM specs on GitHub now :) I'd gladly contribute to fix > this problem but I'm not sure what's the best idea. > > I think it has to be fixed somehow, because people with the latest CentOS > (and I assume also late-ish RHEL) won't be able to use those packages. And > if those guys can't use them, who can? I'm guessing there are some problems > on Fedora and the SUSEs too, because they switched to systemd, no? > > I'd say we address one problem at a time. Should I embed a newer version > of gnutls in the rsyslog package? I'm sure there's a way to tell it > something like "only update if the version you're having is old" or > something it that area. > > If you have other suggestions/solutions, please shoot! > > Best regards, > Radu > _______________________________________________ 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.
