[syslog-ng] load failures in afsocket and afsql

[Martin Holste]

Hm, I know I ran into something similar to this a long time ago, but
I'm having a hard time remembering exactly how I fixed it.  I do
believe that it had something to do with needing to install some dev
RPM's, but I don't want to go on record as saying that will definitely
fix this.  Obviously, though, it might be good to triple-check that
you've got -devel on everything.

Also, since your libs are in a non-standard place, it could also be a
bug in that values that work during the configure step are not getting
passed as macros everywhere they need to be in the make step.  You may
want to try editing your ld.so.conf to include your custom lib
location if you haven't already and running ldconfig -v to make sure
it's being linked.

Finally, if you're building the dependency libs from source as well,
making sure that there aren't any other "make" steps that need to be
done is another one to check off.  I believe some libs need "make
shared" (libpcap, for one).

I don't know if any of these will fix the problem, but they can't hurt
to verify.

On Mon, Dec 13, 2010 at 8:12 PM, Matthew Hall <mhall at mhcomputing.net> wrote:
> I am getting the following on load:
>
> Error opening plugin module; module='afsocket', error='/home/y/lib64/syslog-ng/libafsocket.so: undefined symbol: libnet_build_ipv4'
> Error opening plugin module; module='afsql', error='/home/y/lib64/syslog-ng/libafsql.so: undefined symbol: dbi_result_free'
> Error opening plugin module; module='afsocket', error='/home/y/lib64/syslog-ng/libafsocket.so: undefined symbol: libnet_build_ipv4'
>
> The rpath looks OK:
>
> megahall at logproxy2:~$ readelf -a /home/y/lib64/syslog-ng/libafsocket.so | fgrep -i rpath
>  0x000000000000000f (RPATH)              Library rpath: [/home/y/lib64]
> megahall at logproxy2:~$ readelf -a /home/y/lib64/syslog-ng/libafsql.so | fgrep -i rpath
>  0x000000000000000f (RPATH)              Library rpath: [/home/y/lib64]
> megahall at logproxy2:~$
>
> megahall at logproxy2:~$ ldd /home/y/lib64/syslog-ng/libafs* | fgrep -i '(dbi|net)'
> megahall at logproxy2:~$
>
> The libraries are in a reasonable location:
>
> /home/y/lib64/libdbi.so.1.0.0
> /home/y/lib64/libnet.so.1.5.0
> /home/y/lib64/dbd/libdbdsqlite3.so
> /home/y/lib64/dbd/libdbdmysql.so
> /home/y/lib64/libnet.so.1
> /home/y/lib64/libdbi.so.1
> /home/y/lib64/libdbi.so
>
> Reading through the glib docs for glib modules, it seems like the .la
> files are maybe not containing the right library dependencies, or
> something like this. However adding the library directories using
> LD_LIBRARY_PATH as a temporary test does not help.
>
> Because this step fails, it's not possible to use tcp, udp, or any of
> the other important drivers you need to collect logs.
>
> I could really use some advice on this one!
>
> Matthew.
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.campin.net/syslog-ng/faq.html
>
>