Bug 189554

Summary: mysql-python linked against wrong version of mysql
Product: Red Hat Enterprise Linux 4 Reporter: Jack Neely <jjneely>
Component: MySQL-pythonAssignee: Tom Lane <tgl>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: hhorak
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-04-21 02:32:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Jack Neely 2006-04-21 01:15:17 UTC
Description of problem:
With RHEL 4, loading the php-mysql DSO into apache and using another mysql
system such as mod_python + mysql apache segfaults, gets sigabrt's, glibc
reports double frees, and other unfunness.  This is due to modules linking to
different mysql clients.  This creates conflicting modules loaded into apache.

mod_python has an FAQ about this:
http://modpython.org/FAQ/faqw.py?req=show&file=faq02.013.htp

Please have all apache modules link against the same mysql libraries so that all
the lamp-ish software included with RHEL can be used together.

[root@linux00ws ~]# ldd /usr/lib/python2.3/site-packages/_mysql.so
        libmysqlclient.so.10 => /usr/lib/mysql/libmysqlclient.so.10 (0x00eb3000)
       libz.so.1 => /usr/lib/libz.so.1 (0x00215000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0x002bf000)
        libc.so.6 => /lib/tls/libc.so.6 (0x00d19000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x00c0b000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x00413000)
        libm.so.6 => /lib/tls/libm.so.6 (0x00111000)
        /lib/ld-linux.so.2 (0x003cb000)
[root@linux00ws ~]# ldd /usr/lib/php4/mysql.so
        libmysqlclient.so.14 => /usr/lib/mysql/libmysqlclient.so.14 (0x003e5000)
       libc.so.6 => /lib/tls/libc.so.6 (0x00111000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x008e0000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x00820000)
        libm.so.6 => /lib/tls/libm.so.6 (0x00888000)
        libssl.so.4 => /lib/libssl.so.4 (0x00910000)
        libcrypto.so.4 => /lib/libcrypto.so.4 (0x00eb8000)
        libz.so.1 => /usr/lib/libz.so.1 (0x007f0000)
        /lib/ld-linux.so.2 (0x003cb000)
        libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x0023b000)
        libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00a98000)
        libcom_err.so.2 => /lib/libcom_err.so.2 (0x00788000)
        libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x0024f000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x002f8000)
        libdl.so.2 => /lib/libdl.so.2 (0x009dc000)

Comment 1 Tom Lane 2006-04-21 02:32:16 UTC
Yeah, we know.  It seems that mysql-python is too far down the priority list to get included in quarterly 
update lists, despite being totally broken :-(.  Not my call unfortunately.

*** This bug has been marked as a duplicate of 150828 ***