Daniel Sutcliffe wrote :
>> I have now tracked this down to the fact that I began using the
>> Percona version of the mysql-libs package that contains
>> libmysqlclient.so.16 - obviously some incompatibility there as the
>> original worked but the Percona version cause postfix smtp to segfault
>> over TLS...
>>
>> As far as I am aware I don't use any postfix mysql features so I don't
>> even need to be linked against that library - will this be fixed at
Wietse Venema wrote:
> That eliminates only direct postfix-to-mysql dependencies. The
> problem can still exist with library-to-library dependencies,
> or in NSSWITCH or PAM dependencies that don't show up with ldd<
> and the problem can be in a dependency of Percona mysql-libs.
Understood, thanks for the response Wietse :)
I have now made this work with a kind of Duct tape and string method,
by replacing the smtp binary with this:
> #!/bin/sh
> export LD_LIBRARY_PATH=/usr/libexec/postfix/orig:$LD_LIBRARY_PATH
> exec /usr/libexec/postfix/orig/smtp $*
And placing the good (original) libmysqlclient.so.16 in the orig
subdir, along with the original smtp binary.
Seems to work fine for my current needs but obviously not a good long
term solution - that would be to get Percona to 'fix' their
distributed shared lib so that it is compatible with official
CentOS/RHEL 6 rpms - it should be it is one specific for these
systems.
Out of interest here's the ldd output for the original libmysqlclient.so.16:
linux-vdso.so.1 => (0x00007fff27fc1000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007faafed0b000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00007faafeaf2000)
libm.so.6 => /lib64/libm.so.6 (0x00007faafe86d000)
libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007faafe612000)
libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x00007faafe278000)
libz.so.1 => /lib64/libz.so.1 (0x00007faafe061000)
libc.so.6 => /lib64/libc.so.6 (0x00007faafdcd1000)
libfreebl3.so => /lib64/libfreebl3.so (0x00007faafda6f000)
libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007faafd82c000)
libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007faafd54d000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007faafd349000)
libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007faafd11c000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007faafcf18000)
/lib64/ld-linux-x86-64.so.2 (0x00007faaff2cc000)
libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007faafcd0d000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007faafcb09000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007faafc8ef000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007faafc6d3000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007faafc4b3000)
And for the Percona distributed version:
linux-vdso.so.1 => (0x00007fffc2fff000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa51a222000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007fa519feb000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00007fa519dd1000)
libm.so.6 => /lib64/libm.so.6 (0x00007fa519b4d000)
libc.so.6 => /lib64/libc.so.6 (0x00007fa5197bd000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa51a74c000)
libfreebl3.so => /lib64/libfreebl3.so (0x00007fa51955a000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fa519356000)
Obviously different ...
Thanks for the help in getting to the bottom of this - maybe these
postings will save someone else my headache in future.
Cheers
/dan
--
Daniel Sutcliffe <dan...@tcnow.com>
